For some reason visual studio 2010 crashes and restart on publish to the cloud.
This is specific for one big role (about 50mb).
Visual studio dies just before he opens the status in win azure activity log.
In about 10 attempts one works and the role gets uploaded and started.
VS crash even if I just select to create a package in publish dialog.
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.Build.Shared.InternalErrorException
at Microsoft.Build.Shared.ErrorUtilities.ThrowInternalError(System.String, System.Exception, System.Object)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
This is the crash report tha VS creates:
Sig.Name=Problem Signature 01
Sig.Name=Problem Signature 02
Sig.Name=Problem Signature 03
Sig.Name=Problem Signature 04
Sig.Name=Problem Signature 05
Sig.Name=Problem Signature 06
Sig.Name=Problem Signature 07
Sig.Name=Problem Signature 08
Sig.Name=Problem Signature 09
UI=C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
UI=Microsoft Visual Studio has encountered a problem and needs to close.
UI=If you had files open that contained unsaved changes, these changes might be lost.
UI=Check online for a solution and restart the program
UI=Check online for a solution later and close the program
UI=Close the program
AppName=Microsoft Visual Studio
AppPath=C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
This drives me crazy, and it is a big waste my time. Please help, I don't know what other info I can post.
It seems the problem is specific with the application which you mentioned is about 50MB. The application/package size should never be the problem however I think this
problem is specific the application specific.
First I would try to see if my simple HelloWorld app gives the same problem or not and if yes then it could be tool specific issue means some of the components are
not installed properly otherwise application specific.
To investigate I would suggest running Process Monitor to log process and file system activities to see when the crash occurred what file/registry was being accessed.
If problem happen 90% of the time and build works 10% of the time, you will have the log for both working and non-working case to isolate the files/registry.
After that I would check with those files and setting to understand why there is the error. You can use Azure Support team to investigate this issue as well
For example, VS2010SP1 to crash in the following cases.
1. Web application project, for example, about 20 MByte PDF file contains.
2. This file's Build Action property is Content.
3. This file Copy to Output Directory property is Copy always.
In this State, Publish > Create Service Package Only.
During the cspkg file is not created successfully.
It seems the cspack is being terminated abnormally.
Even if successful, larger file size.
Problem does not occur when you change the file properties.
1. Do not copy this file Copy to Output Directory property.
I am experiencing the same issues here. Visual Studio crashes when publishing and I have been chasing this for HOURS. What a pain. Also, on the few occassions that it has created the publishing files it runs for an hour+ and then fails
because the packages are too big. It seems that publishing doesn't create a consistent size and I get 700MB+ files
I believe that this issue is related to another issue with memory. In our application we are always getting out of memory messages when trying to build the application. We are using windows 7 - 32 bit with 2 GB RAM. I just changed the
memory to 3 GB and the publish worked...could be a coincidence. I will have to see after publishing it later.
I was seeing the same issue when the active solution build configuration was mismatched with the Azure packaging build configuration. Setting both of these to same configuration (Debug or Release) reliably solved the problem.
Proposed As Answer bysilijonFriday, February 03, 2012 1:47 AM
I came up against this as well. I have a couple pieces of information:
1.I talked to Microsoft Azure support and they said its a known bug and will be fixed in the next version (I'm using azure tools 1.6). They also said you could work around it by building the package and deploying outside of Visual Studio, although I have
not tried this.
2. I have been able to get my site to deploy reliably without crashing if I go into my azure project folder every time before I deploy and delete the subfolders
bin,csx, and obj.