Since the release of Visual Studio 2010 we have received a few reports of crashing behavior which can be traced back to issues with MSBuild. We’ve analyzed all of these and there are several particular cases where a crash can occur. We’ve also added a notification to Windows Error Reporting to help guide those who hit these errors. You can determine you your error is one of these either by matching the problem description below, or looking in the Event Viewer as follows: Open the Event Viewer
Search for Information events with ID = 1001 and Source = Windows Error Reporting. Look for those with the time that approximately matches when you saw the crash.
At the top of the details pane for the event is text that would look like the below. If the bucket number is not 1055654512, then this post may not apply to you.
Fault bucket 1055654512, type 1Event Name: APPCRASHResponse: xxxxxxxCab Id: 0Crash when debugging using F5Problem: This can occur if the build process is missing a required target. This is normally due to an improperly customized build process. If you are using the .NET MicroFramework 4, which is not supported in Visual Studio 2010, you may also see this issue. Solution: Provide the missing target. Try building the project/solution on the command-line. If MSBuild logs an error that a target is missing, that could be the problem. Crash when registering COM component Problem: COM registration requires the user have permission to certain registry keys, and lacking that permission the RegASM task crashes.Read more: The Visual Studio Blog
Search for Information events with ID = 1001 and Source = Windows Error Reporting. Look for those with the time that approximately matches when you saw the crash.
At the top of the details pane for the event is text that would look like the below. If the bucket number is not 1055654512, then this post may not apply to you.
Fault bucket 1055654512, type 1Event Name: APPCRASHResponse: xxxxxxxCab Id: 0Crash when debugging using F5Problem: This can occur if the build process is missing a required target. This is normally due to an improperly customized build process. If you are using the .NET MicroFramework 4, which is not supported in Visual Studio 2010, you may also see this issue. Solution: Provide the missing target. Try building the project/solution on the command-line. If MSBuild logs an error that a target is missing, that could be the problem. Crash when registering COM component Problem: COM registration requires the user have permission to certain registry keys, and lacking that permission the RegASM task crashes.Read more: The Visual Studio Blog
Posts
0 comments:
Post a Comment