Visual Studio 2015 exit code 0xE0434352 - winforms

Question

I have a build script which starts Visual Studio from a command line as follows:
devenv.exe <project file> /Rebuild "Release" /Project <project name> /UseEnv /Out <log file>
On completion the script checks the exit code from Visual Studio.
We have updated from Visual Studio 2010 to 2015. Most of the projects compile without problems, but some exit with the code 0xE0434352, which I believe is System.InvalidOperationException.
The windows event log shows two entries:
Faulting application name: devenv.exe, version: 14.0.24720.0, time stamp: 0x564ea97e
Faulting module name: KERNELBASE.dll, version: 6.1.7601.19045, time stamp: 0x56258f05
Exception code: 0xe0434352
Fault offset: 0x0000c42d
Faulting process id: 0xb64
Faulting application start time: 0x01d131c68bdc0db0
Faulting application path: c:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: cb600c61-9db9-11e5-abfc-005056c00008
and
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
at System.Windows.Forms.Control.MarshaledInvoke(System.Windows.Forms.Control, System.Delegate, System.Object[], Boolean)
at System.Windows.Forms.Control.BeginInvoke(System.Delegate, System.Object[])
at System.Windows.Forms.WindowsFormsSynchronizationContext.Post(System.Threading.SendOrPostCallback, System.Object)
at System.Threading.Tasks.SynchronizationContextAwaitTaskContinuation.PostAction(System.Object)
at System.Threading.Tasks.AwaitTaskContinuation.RunCallback(System.Threading.ContextCallback, System.Object, System.Threading.Tasks.Task ByRef)
at System.Threading.Tasks.AwaitTaskContinuation+<>c.<ThrowAsyncIfNecessary>b__18_0(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
The projects are VB and C# Windows Forms projects. It is not happening with C++ projects.
So far as I can tell, the components are always built correctly and the exception occurs on closing visual studio. I have modified our script to ignore this specific error, but that doesn't seem like a great solution.
Can anybody suggest how to fix this problem?

Answer 1

If that are all normal projects you build you don't need devenv to do that work for you.
Simply use msbuild.
I think this commandline should get you started:
msbuild /t:Build /p:Configuration=Release [your .sln or .csproj or .vbproj]
Which instructs msbuild to process the Build target and set the Property named Configuration to Release
Notice how you can either msbuild the complete solution or single projects this way. The only exception is for projecttypes that are only known to Visual Studio and not to msbuild. For earlier versions of VS that was true for the Setup projecttype. You couldn't build that one without running devenv.