Re: converting from DOS/Visual Studio to Ant for build

[Alexey Solofnenko]

We did the opposite - converted all ANT scripts that build .Net and C++ code into a VisualStudio build (that we execute from ANT script itself). The main reason is to avoid double maintenance. It is useful to have a single "build" solution that builds only necessary (for delivery or for tasting) projects. We also implemented extra build steps using MSBuild commands and put them in the project files themselves (in fact one of the project even runs ANT to build prerequisites). There were many complains from people from other groups that it was difficult to build my project's Windows applications - now all necessary parts are done by just pressing build or run from VisualStudio.

- Alexey.

weiji wrote:

I would advise against porting VisualStudio build to ANT - VisualStudio build is usually enough and it and ANT builds can call each other without any problem.

Hi,

Our current build process involves a DOS batch file to loop through a list
of solutions that we want to build, and invoking the command line Visual
Studio client to build each one.  We are interested in Ant as a replacement,
since we believe the logic control/conditional execution of targets will
come in very handy.  However, first we need to get it working as a
functional replacement for our current needs.

There are two parts we need to get working first.  The list of solutions to
build is manually maintained (and is a subset of the directories under our
solutions directory).  The first issue is to figure out how to pass this
list of solutions into Ant. The second issue is how to invoke the same
target for each solution, passing the name of the solution to the exec task.

Any suggestions or alternatives are highly appreciated.

Thanks in advance,
KaJun

--
------------------------------------------------------------------------
Alexey N. Solofnenko <http://trelony.cjb.net/>
Pleasant Hill, CA (GMT-8 usually)

smime.p7s
Description: S/MIME Cryptographic Signature