Created an Empty Unit Test Project, Clicked Build - Visual Studio Became Unreponsive - by DJ PIP

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<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 771481 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 11/17/2012 6:20:35 AM
Access Restriction Public


I created a new .NET 4.5 Unit Test Project as part of an existing solution. Before writing any unit tests, I clicked Build. Visual Studio became unresponsive during the build process and refused to let me cancel the build nor would it complete.

Sign in to post a comment.
Posted by DJ PIP on 11/22/2012 at 3:15 AM
Please close this issue - unfortunately I do not have the dump file available to re-upload and I haven't encountered the problem again since. If it does happen again I'll create another report.
Posted by Microsoft on 11/19/2012 at 7:11 PM
Thanks for your feedback.

We are sorry that we cann't get the dump file. Maybe it is too large. Please try uploading it througth my workspace again. It would be better if you give us a simple repro project.

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


You can use the following workspace to upload the file:

Password: uun0CGz4T+x+

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

Please submit this information to us within 4 business days. We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 11/19/2012 at 9:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(
Posted by DJ PIP on 11/17/2012 at 6:35 AM
I've attached a dump file of the Visual Studio process whilst it was stuck building the project. It did not appear to be 'Unresponsive' in task manager, however the process was using 25% of the CPU on my Quad Core PC.