When calling devenv.com from command line or FinalBuilder action within our automated build it sometimes hangs and never gets past compiling step.
It is called with this parameters from C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE:
devenv.com /build "Release|Any CPU" "D:\MyProject\MySolution.sln"
It hangs forever on this step. When I open it in VS 2013 and ReBuild the solution it works fine every time.
Any ideas? I've also tried it on other build machines and it does the same. So it is not machine dependent.
Devenv lets you set various options for the IDE, build projects, debug projects, and deploy projects from the command line.
Press windows + r to open run window and then write "regedit" to open your PC registry. Then go to HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Windows -> Currentversion -> App Paths -> devenv.exe. Click on devenv.exe and change the value of default .
Devenv uses MSBuild to build projects, but MSBuild does not build Visual C++ Projects. If MSBuild comes across a solution that includes Visual C++ projects, it will call VCBuild. If the projects are using C++, then MSBuild is not called.
After a lot of troubleshooting and looking through various logs, solutions, googling, I figured out that this is caused by the Extension Manager in Visual Studio 2013. You can find the extension manager in all Visual Studio version -> Tools -> Extensions and updates.
So by uninstalling the Nuget Package Manager from Visual Studio 2013, made it the solutions compile successfully every time.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With