It
would seem to me from a maintenance standpoint that you should stick with all
developers just building in visual studio. Why push 10 cars when you can
drive one bus? Let VS.Net do the work when you are developing.
Then create a build process on your master build machine that is
tweaked to what you need for testing/production.
With
the new functionality of NAnt, you shouldn't have much difficulty converting
your SLN file into a buildable set of projects. NAnt can do all the work
of extracting the SLN and project code from VSS and building it as the SLN
dictates. Then you don't have to worry when changes are made to the
solution. Depending on your projects and configurations, you can then
set up NAnt to "distribute" your web project to
test/production servers.
Peter
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Cohen, Noah (CA - Ottawa) Sent: Thursday, July 31, 2003 12:44 To: [EMAIL PROTECTED] Subject: [Nant-users] NAnt build for vs.net web project best practice? Hi,
I'm using VSS as the source code repository, along with VS.NET for creating my own soln and csproj files for the web app solution, using the c# and asp*x files from VSS.
My question is what is the best method to build the project? Converting sln files to nant build files or just making an nant build file compiling all cs files and copying necessary asp*x files?
Since we all have our own projects and sln files locally which use the files from VSS, which would be the best method to do a "universal" build that each developer that can perform locally? I'm leaning towards the second mentioned option.
Thanks in advance, - Noah -
|
- [Nant-users] NAnt build for vs.net web project b... Cohen, Noah (CA - Ottawa)
- Peter Lanoie