Batch build .net solutions - seems unreliable

[JamesMaeding]

I have about 10 solutions I need to build every time I tweak a particular library.

I am using VS 2010, all files are C#, no vb or c++ mixed in.

my batch is like:

devenv /build Release "C:\somepath\someprog1.sln"
pause
devenv /build Release "C:\somepath\someprog2.sln"
pause
devenv /build Release "C:\somepath\someprog2.sln"
pause

....

and they all build "sucessfully", but I sometimes get the message at the end that 1 [project] was skipped.

That is no good. Is it common to have issues with command line compile when IDE works fine on every one?

Is there a more prefereed way to build via batch?

[fieldguy · Accepted solution]

can you use /rebuild?

http://stackoverflow.com/questions/4416888/what-is-the-difference-between-a-build-and-a-rebuild-in-v...

[CADbloke · Accepted solution]

Fieldguy is on to something with "rebuild". MSBuild / Devenv will skip builds on code that hasn't changed.

Generally the preferred way to batch build .NET stuff is with MSBuild.exe. See http://msdn.microsoft.com/en-us/library/ms164311.aspx and also for a handy way to find the right MSBuild.exe to use in a batch file.

an example from one of my batch files (using the above SO method to find MSBuild) ...
"%MSBUILDDIR%msbuild.exe" "C:\path\solution.sln" /t:build /p:Configuration="Debug " /detailedsummary

Discussions on this galore at https://www.google.com.au/search?site=&source=hp&q=msbuild+devenv&oq=msbuild+devenv

[JamesMaeding]

yah, the rebuild was the issue.

All the documentation focuses on options, the rebuild never occurred to me, thanks all!