Here's the situation:
- I have a VS2003 Solution that consists of multiple projects. A few projects have dependencies on the others.
- We maintain our source code in Subversion.
- We have multiple developers manipulating/adding code to the repository for all projects contained in this solution.
- Subversion projects correllate to the projects in the solution.
- We don't include .csproj files in the repository. Presence of the files in the repository implies inclusion in the particular project.
My goal:
- Create a build routine that uses NAnt, Subversion and/or any other utilities to automate our builds.
- Zero manual management of .csproj files on the build system. I want those files to be created/managed automatically.
- Very limited manual management of the NAnt build script.
My questions:
- Do I require the individual .csproj files to be current for a NAnt build script? Do I have other options to use besides those files?
- How can I maintain the .csproj files automatically as a result of an svn update?
- Can I avoid the use of .csproj files altogether for the build routine? If so, can I construct the build script in such a way that I'm not required to provide specific file/folder names?
- Is there a better way to go about this?
I'm certain someone else has run into this, but I haven't made much progress in my research thus far this week. Any help or guidance is greatly appreciated. Links to information that point me in the right direction are welcome.
Thanks.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users