VS 2012 Crashing when trying to run Publish - by PaulHN

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 747721 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 6/8/2012 10:16:19 AM
Access Restriction Public


When running Release configuration Publish of VS 2012 RC the dev environment crashes and needs to be restarted. This same project publishes fine in VS 2010.
Sign in to post a comment.
Posted by tofutim on 1/16/2013 at 10:52 AM
I'm having this problem on RTM. The moment I click Publish VS2012 window is unresponsive.
Posted by SliverNinjas on 7/18/2012 at 12:20 PM
Verifying Web Tooling Extensions update fixes the problem. Great job MS!
Posted by Microsoft on 7/13/2012 at 4:45 PM
Hi Paul,

I have some good news! We've just released an update for VS2012 RC which contains the fix for this issue. You can find more information at http://blogs.msdn.com/b/webdevtools/archive/2012/07/12/visual-studio-2012-rc-web-tooling-extensions-update.aspx.

- Jimmy Lewis
SDET, Visual Web Developer team
Posted by Microsoft on 6/15/2012 at 11:58 AM
Hi Paul,

There is a bug in VS2012 RC where this crash will occur if the .pubxml file for your publish profile is marked as Read Only. If you make it writeable, the crash should be avoided.

This is fixed internally and will be released in the next VS2012 release.

- Jimmy Lewis
SDET, Visual Web Developer team
Posted by Microsoft on 6/15/2012 at 12:56 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by PaulHN on 6/14/2012 at 8:02 AM
I have uploaded the requested files. I still get the VS crash when publishing solutions.
Posted by Microsoft on 6/14/2012 at 1:51 AM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 6/10/2012 at 7:27 PM
Thanks for your feedback. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.
It may help if you provide us with Bucket ID, a dump file and call stack.

Bucket ID:
1.    Open Event Viewer        
2.    Click on Windows Logs -> Application
3.    Search for a 1001 event that occurred soon after you encountered the crash
4.    The bucket ID should be available in the event details
(there may be multiple 1001 events for any given crash - only one will have the bucket ID)
Dump File and Callstack:
You can get detailed steps about how to get the dump file and call stack at http://blogs.msdn.com/debugger/archive/2009/12/30/what-is-a-dump-and-how-do-i-create-one.aspx

Please zip the file and use "FeedbackID-747721" as prefix of the file name.

You can use the following workspace to upload the file:
Password is TyDSc*u3LZB

Thanks again for your efforts and we look forward to hearing from you.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 6/8/2012 at 10:52 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)