Using devenv.exe from the command line and specifying the platform
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe” myproject.sln /Build “Release|x86
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe” myproject.sln /Build “Release|x86
Try this ( from MSFT support ) Can you check if the dll is in the global assembly cache (open a VS 2010 command prompt (Start | All Programs | Microsoft Visual Studio 10.0 | Visual Studio Tools)) Type in Gacutil –l > list.txt Notepad list.txt Do you see an entry like Microsoft.VisualStudio.QualityTools.TestCaseManagement, Version=10.0.0.0, Culture=neutral, … Read more
The main advantage of MSBuild is that you don’t need to have Visual Studio installed. One limitation of MSBuild is that it does not support building Visual Studio setup projects (.vdproj). (You can work around this by defining an exec task which calls devenv, but then you still need Visual Studio.)
Update for those who got this issue for VS2013 or VS2015 after upgrading a VS200X setup project using the Microsoft Visual Studio Installer Projects extension. Following the recipe for v1.0.0.0 from MS finally made it work for me: Microsoft Visual Studio Installer Projects Unfortunately we couldn’t address all cases of the command line issue for … Read more
msbuild test.sln /t:project /p:Configuration=”Release” /p:Platform=”x86″ /p:BuildProjectReferences=false Notice that what is assigned to /t is the project name in the solution, it can be different from the project file name. Also, as stated in How to: Build specific targets in solutions by using MSBuild.exe: If the project name contains any of the characters %, $, @, … Read more
you must kill child process too if any spawned to kill successfully your process taskkill /IM “process_name” /T /F /T = kills child process /F = forceful termination of your process