I recently installed Update 1 for Visual Studio 2013. Every time my program throws an exception, the Visual Studio debugger crashes - whether or not the exception is handled.
Visual Studio also crashes whenever it hits a breakpoint.
The Windows Error Reporting dialog pops up and gives the options to debug or restart Visual Studio. If I click debug and and open with VS, it also crashes - debugging itself! This is leading me to believe that there is not a problem with my app, but rather with Visual Studio.
Visual Studio Professional 2013 (12.0.30110.00 Update 1)
Windows Server 2012 R2 x64
Any ideas?
The problem, it turns out, was that I had installed a trial version of Redgate Tools' .NET Reflector. The trial's expiration had coincided with my installation of Update 1. .NET Reflector was throwing a NullReferenceException and hence crashing Visual Studio.
The solution was simple: disable or uninstall the .NET Reflector extension.
My proposal is: get more data about the crash and see whether it's caused by Visual Studio itself or any plugins which might not be compatible any more.
Set up the registry for Windows Error Reporting to store local dump files, reproduce the crash and analyze the dump in WinDbg (because Visual Studio is not working well).
Some steps in WinDbg:
open crash dump
.symfix c:\mysymbols
.reload
.exr -1
.loadby sos clr (if it's a .NET exception)
!pe (if it's a .NET exception)
!clrstack (if it's a .NET exception)
I also get Problems with IDE crashing after installed "update 1". My Workaround: uninstall that update. It is really Buggy and NOT production ready. Maybe it is caused by a Extension, but I dont have time to debug Tools I have to use to get my work done, I Need working Tools.
I've been stuck in this problem for 3 days until I discovered that the problem was in try-catch blocks. Viewing this article: http://msdn.microsoft.com/en-us/library/vstudio/0yd65esw%28v=vs.110%29.aspx, I realized the importance of not leaving a "catch" empty.
Well, this problem happened to me while developing a simple sequential workflow SharePoint 2013 in Visual Studio 2013 in "OnTaskChanged" methods.
I hope the answer may help someone else.
Related
Recently started using Visual Studio 2012, converting SSIS packages from 2008, and seem to be unable to set breakpoints in Script Tasks. The error we're receiving says
Cannot start debugging. Pre-debugging negotiations with Host failed.
Cannot seem to find any information about this error, or what's causing it. There is also a brief flash of a dialog box that says
Visual Studio has encountered an unexpected error
but that disappears quickly.
This issue has been resolved. The input parameters were set incorrect and hence was failing. It has been fixed now
I think you install new version of Visual Studio you just have to uninstall the Visual Studio tools for Application for the new version then repair the Visual Studio tool for Application 2012 and every thinks will be good
I have the problem that Visual Studio 2013 crashes when I lock the computer or start another instance of Visual Studio.
I use Visual Studio 2013 with latest patches applied. I always start Visual Studio as Admin.
This seems to only happen with a certain big solution. This problem did not occur to me with other solutions.
I tried to delete the solution and make a clean checkout from TFS, but Visual Studio still crashes.
I know this is not much information, but do you have any idea how to fix this or how to what else I could check?
Additional Information: This still happens even with Visual Studio 2015 on a fresh Windows 8.1 installation...
Here's the error:
Use the following steps to solve the issue:
Source: http://resharper-support.jetbrains.com/entries/24765142-Visual-Studio-with-ReSharper-is-freezing-and-or-crashing
I would copy the solution with quotation but as you can see, there is a lot of text to edit.
Start Visual Studio using the /log switch. Then check the created log file for warnings and errors:
%APPDATA%\Microsoft\VisualStudio\11.0\ActivityLog.xml
If you use a Web Browser to view the file, it will be nicely formatted, due to the accompanying xsl-sheet.
Visual Studio 2013 is crashing with an exception - An exception was thrown by a taskscheduler.
I am unable to resolve this issue, searched but could not get any useful information on this.
Need help to resolve it.
many time when we update our .NET Framework then this problem is occurred. Check if you update your version of .NET Framework then uninstall that and also repair visual studio.
I could not even uninstall/repair the Visual Studio. When i clicked on the Visual Studio from the Control Panel, even the uninstall wizard did not come up.
The solution which worked for me is:
When I saw the GAC_MSIL, many dll's were missing, then i copied System.dll, System.Core.dll and System.Reflection.dll into the GAC_MSIL. After copying these dll's , from the control panel the uninstall wizard started, and then i repaired the VS 2013. Then it worked.
I also saw this sort of crash in one of my VMs, in that scenario, i copied the above dll's and VS started working.
I can't debug my Sharepoint 2010 project. Visual Studio 2010 shows me the following error message:
Unable to attach to he process. An error occurred that usually indicates a corrupt installation (code 0x80040154). If the problem persists, repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel.
I experienced this problem some days ago for the first time.
At first repairing helped, but after a little time the error occurred again.
I have tried restarting computer, too, after which the problem was gone for only a little time.
I have uninstalled/reinstalled visual studio, but still no success.
How can I solve this problem, I have no idea about the reason.
EDIT: I have noticed that the problem occurs only when I try to debug a workflow code.
I have had this issue in the past and solved it by ensuring I'm compiling the code to x64. Check your settings in Visual Studio. SharePoint is 64bit only.
Good Luck.
I had a problem with the javascript debugger on a web project, and I got a similar error message. The fix was: Closed all instances of Visual Studio. I threw away the app in inetmgr, and re-opened visual studio with my solution that has my web app. It re-created the virtual directory on opening. Javascript debugger started working again.
My dev machine got the automatic update from IE9 to IE10. The latter is broken on our development web site, so I uninstalled the IE 10 "update" to revert to IE9.
Visual Studio 2010 will no longer attach its debugger to the browser. I can either debug in IE9 developer mode, or attempt to launch a new instance of VS'10 to debug (but that doesn't work either.)
What can I do to restore the link between VS'10 and IE'09?
EDIT:
I get the dialog titled "Visual Studio Just-In-Time Debugger".
"An unhandled exception ('Script Breakpoint') occurred in iexplore.exe [4824]
Possible debuggers:
New Instances of Microsoft Visual Studio 2010
....
"
I cannot attach to the already running instance of VS.
Try to re-install the .net library.
.Net Library
This post suggests a solution:
Here's the solution: The key is that the message says the incorrect
version of pdm.dll is not registered. Apparently the IE10 install
provided a new pdm.dll and the re-install of IE9 did not replace it. I
found an older version on another system, copied it to the C:\Program
Files\Common Files\microsoft shared\VS7Debug folder, registered it,
and now VS2010 debugging works again.
However, I'm not yet sure how to download the file called for in this solution.