Francis Norton wrote:
Gordon Weakliem has written a csproj transform - follow the link from his blog about it at http://radio.weblogs.com/0106046/stories/2002/08/10/supportingVsnetAndNant.htmlThe disadvantage of my method over SLiNgshoT is that you have to maintain a master build file that you keep in sync with the SLN, while SLiNgshoT can read the SLN and do it for you. However, in our case we have 4 or 5 solutions that all get deployed together, so SLiNgshoT wouldn't buy us much, and we also have some funny deployment things (i.e. 4 web services with separate .sln files that end up living in the same webapp, so we have to make sure only one assembly has the Global.asax.cs compiled in). So I manually maintain the master build, which changes only when projects get added or deleted, which isn't often. What I did is to make the master build implement the same targets as the individual project builds, but the master simply delegates to each project using the <nant> task. Which ends up being a lot of cut and paste, so the master's a bit ugly, but I don't have to look at it often. Have a look at the article Francis linked to and I can try to fill in any gaps that are left.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Nant-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-users
