My Isolated Shell app is now suddenly giving this crash on exit that I have no idea of where it comes from.
Here are the details Windows give:
Problem Event Name:APPCRASH
Application Name:<omitted>.exe
Application Version:1.0.0.1
Application Timestamp:541c3849
Fault Module Name:msenv.dll
Fault Module Version:12.0.30723.0
Fault Module Timestamp:53cf6f1e
Exception Code:c0000005
Exception Offset:0001e974
OS Version:6.1.7601.2.1.0.256.4
Locale ID:1033
Additional Information 1:0a9e
Additional Information 2:0a9e372d3b4ad19135b953a78882e789
Additional Information 3:0a9e
Additional Information 4:0a9e372d3b4ad19135b953a78882e789
When I debug this isolated shell from VS, the same access violation occurs, and the file crtexe.c opens up. Again, not even close to any part of my code.
The only thing I did recently was installing the VS 2013 Update 3, since I had to install the Azure SDK and it forced me to update VS.
So now I am running VS 2013 Pro v12.0.30723.00 Update 3. My Isolated Shell app consists of a few VSPackages deriving from the Managed Project Framework. I am developing it for a full year now, and never had this kind of problem before.
Another, perhaps related, question is if Microsoft will ever release updates the VS 2013 Isolated Shell redistributable like its doing with VS 2013. I dont know if this can be a problem, but my appenvstub.dll is still on version 12.0.21005.1.
EDIT 1: Even creating a new Isolated Shell from scratch gives the same result. It always crash on exit. Next thing on my list is running a repair/reinstall of Visual Studio and all of its updates, which will consume at least half of my day :(