build process - MSBuild vs. NAnt for a mixed 2005 and 2003 codebase -
We currently maintain a huge code base with hundreds * .proj and maybe solution with 50 interdependence.
All our code base are either .NET or legacy C ++.
The current creation process is the nested command line script that pulls the automatic source control and then makes each solution by calling devenv. Exe
I want to take advantage of some better building and deployment equipment and I feel that I am either living between NAT or MSBild.
Here is the RABI:
About half the code is being created under Base Visual Studio 2003. The second half is 2005. It is not currently politically feasible to transfer it to the current IDE because it will require re-testing and introduction risk.
My question is - Has anyone successfully used MSBuild to build the heritage of 2003? Can I easily create custom functions that call our legacy solution devenv.exe?
Or should I just consider this time?
I think a hybrid approach can be the best here too. Simply use your MSBuild script for VS2005 projects, and build a NNP script for the old VS2003 projects. If you need build script to manage both, the NAND to control the process along with the task Use
The negativity here is that you have to maintain some knowledge of the two build systems, but my condition is that you want to migrate to MSBuild for a long time.
Comments
Post a Comment