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.
Related
For a few days now, whenever I try to start Visual Studio 2017 I get an error that says that an specified procedure couldnt be found
I have tried the .NET Framework repair form Microsoft and it couldn't find the problem, I have also tried uninstalling and installing Visual Studio 2017 but the installation also throws the error (though it finishes and I can try to open Visual Studio again).
I have tried the .NET Framework installers but they say the framework is already installed so it won't do anything, and I can't find any way to uninstall .NET Framework in Windows 10.
I searched through Google for some versions of the DLL and putting it in the C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder but none have changed anything.
I recently installed Visual Studio 2017 on my laptop (running Windows 10). I have a C++ project using the OpenCV and Eigen libraries, and it seems to compile correctly, but when I try to run the Local Windows Debugger, I get an error message that says:
Visual Studio Remote Debugger (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual Studio installation via 'Add or Remove Programs' in Control Panel
I ran the Repair tool it suggested, with no luck. I also checked for a solution online, and came across a support page (Link). I tried turning off my anti-virus and firewall as per the suggestions on the support page, but that didn't get rid of the error message. My laptop is brand new, and I just installed Visual Studio and the Remote Debugger, so I don't think it would be the case that the version of the Remote Debugger doesn't match with that of Visual Studio. All of the other suggestions are for people doing remote debugging, but I'm doing a local debug.
Any help/suggestions on resolving this issue would be appreciated.
Firstly close the Visual Studio.
Goto AppData\Local\Microsoft\VisualStudio and select version (Ex: VS 2015 has 14.0 folder).
Then delete ComponentModelCache folder.
Start the Visual Studio.
Find what's preventing msvsmon.exe from running.
I encountered this error in Visual Studio 2019 while trying to start debugging a .net 5 console application. I tried to run C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\Remote Debugger\x64\msvsmon.exe and found that User Access Control dialog opens and is asking to run it as an administrator. So two solutions were possible for me, either run VS2019 as Administrator or remove the Run this program as an administrator setting for msvsmon.exe.
I have Visual Studio 2013 which included "PreEmptive Dotfuscator and Analytics".
It's always worked fine for me until recently.
Suddenly it will not open from Visual Studio, icon or commandline.
Even when I manually open it, it does not show up in the task manager.
It simply does nothing.
There's nothing in the Event Viewer logs.
Visual Studio shows no error.
Basically, I can't even begin to find the problem.
I tried to find a download to attempt to reinstall it but all I've seen on the website for this version is that it's included in VS2013.
There's other sites in search results which claim to have the installer but none I trust.
Has anyone had this issue in the past?
It's Visual Studio 2013 Professional on Windows 8.1.
I'm not sure how to address this so I would greatly appreciate any possible input.
Thanks in advance!
You can try uninstalling, wiping the settings, and reinstalling. Dotfuscator Community Edition is uninstallable via the Windows control panel. Once uninstalled, delete %LOCALAPPDATA%\PreEmptive Solutions. You may be able to reinstall it as a component via the Visual Studio installer. If not, it is actually a standalone installer, so if you have a Visual Studio disc or .iso, it will be in \packages\Dotfuscator.
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 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.