We use Make to compile our product, which includes C, C ++, Java, and many other bits and parts. As far as possible, we have all the tools necessary to compile everything that is checked in the source control, to eliminate local dependencies and ensure consistency between dev machines.
We recently added some components written in C # using Visual Studio and would like to use a similar approach with Visual Studio solutions. Disabling up is devenvnot a good option. Calling csc.exedirectly (as I already did before using Nant ), you will need to track the dependencies of the files in the script assembly, which I would rather just allow the Visual Studio solution.
MSBuild seems like a good bet, although its default location %windir%\Microsoft.NET\Framework\[version]\makes me worry about the variability between machines, both with [version] on the way and the fact that you will see the "Framework" and "Framework64" directories. I would not mind that all developers have a version of the .NET framework, but I'm worried that your v3.5 might not be the same as mine.
Does anyone have a solution that they like? Tried everything you really didn't like?
source
share