ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <>
Subject Re: Recommendations for moving from java to .NET
Date Wed, 05 Feb 2003 18:07:27 GMT
out of curiousity, why the migration?

The .NET tools in ant are all you get with ant, though in CVS there are
better versions, versions that support definitions as inner elements,
compile VB, etc, etc. But these are unstable and will change again before
ant1.6 ships, and not fully documented until you run the proposal/xdocs
build file to autogenerate the documentation.

Nb, the changes I want to do before ant1.6 to this code are
-fix up references so you can have filesets of libraries <references
dir="lib" includes="**/*.dll" />

-add code to look at the PE header of a DLL, and drop all 'unmanaged' dlls
from the reference set above. This lets you auto include only the PE
libraries, not legacy libs (that the compiler barfs on)

-ideally integrate defines and references with the defines and lib datatypes
in ant-contrib's C++ routines, so we only have one set of these low level
datatypes (in ant core)

----- Original Message -----
From: "Nau, Michael" <>
To: <>
Sent: Wednesday, February 05, 2003 09:39
Subject: Recommendations for moving from java to .NET

We are looking into shifting our component-based development environment
from java & j2ee to c# & .NET.

Has anyone used the .NET tools provided in ant
( Does anyone
have any other recommendations?

Any advice would be greatly appreciated.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message