Ken Witmyer wrote:
The developers are understandably not too keen on the idea of manually
maintaining these references in the build scripts. They have proposed
hooking into VS.NET's build process to mine the .csproj files and
rebuild the csc tasks in the build scripts. I'm a bit hesitant
because I'd rather not abstract and automate the build scripts too
much (for various reasons) plus I'm not a huge fan of integrating with
VS.NET so that the user is forced to rebuild their build scripts every
time they compile.
I don't follow the last point. If you're integrating with VS.Net, why
would users have to rebuild their build scripts?
At what level do the version numbers change? Is it possible to set up
your config files so that the differences in version number ceases to be
a problem?
Gary
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Nant-users mailing list
Nant-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users
