I can't launch VS 2010 (on Windows XP), every time this error "exception thrown by the target of invocation" keeps showing.
I have checked the length of PATH variable, it is under 2048 so this is not the cause.
What else might cause the problem?
seems like Windows explorer causes this issue, I am not sure.
My OS: Windows 2008 R2 (using as desktop), running VS 2010 and VS 2013 both.
When I started VS 2010 today morning, got this exception:exception thrown by the target of invocation.
I killed the explorer.exe from task manager, and started again use the task manager File->New Task -> Explorer.exe.
Start VS 2010 - Worked fine.
Hope this helps
Related
I have just installed Visual Studio 2015 Update 2 on my Windows 10 machine (both x64 versions) and I am having hard time getting the debugger to work. When I try to attach to any process via Debug menu, I keep on getting:
I have tried reinstalling, repairing Visual studio few times always get the same error. Even running a basic hello world console application gives the same error.
When trying to run a web application using the IIS Web Express 8/10.
Even though I am absolutely sure that the message of corrupt installation is misleading, but I even have tried repairing visual studio from control panel and nothing seems to work. I dont even get any error logged anywhere which is keeping me stumped for last 1 day. This is what my VS installation looks like:
I am running the visual studio as administrator. I am pretty sure this is not a windows error as I tried installing VS2012 and debugging works in it.
Any ideas?
I have some web projects that run fine in the debugger in VS 2012. But when I try to run the same projects in VS 2013 i run into some problems.
First the whole Devenv.exe crashed when pressing F5.
I found an article about this problem here
It suggests set ISS Express in Visual Studio to 64 bit.
That solved the problem of the whole IDE crashing.
However, with that configuration Visual Studio tries to start "Remote Debugging". Probably because Visual Studio itself is 32 bit, so it must use some "remote" techniques to debug something 64 bit. At least that's my guess on what is happening.
Remote debugging is not succeeding either. I get "Remote Debugger has stopped Working" sometimes. Sometime at the beginning of the degugging session, and sometime at the end of the session. I found an article about this problem too. It suggest to set the web project to x86 to avoid remote debugging. But that will not work in this case. It has to run 64 bit to work with IIS in 64 bit.
Error message is
Remote Debugger has stopped Working
Then
The debugger's worker process (msvsmon.exe) unexpectedly exited. Debugging will be aborted.
Anyone else seen this?
Is this a common problem in Visual Studio 2013?
EDIT: more details about the environment
I have a solution containing several projects, including two web projects.
The issue happens when I try to run any of the web projects in debugger (by pressing F5).
They are normal web projects, and I am not running anything remote.
Visual Studio itself came up with the idea of using "Remote Debugger" when I checked the "Use the 64 bit version of IIS Express for web sites and projects".
The solution was first created on a Windows 7 machine running Visual Studio 2012 and it worked well there.
When I tried to open the same solution on a new machine running Windows 8.1 and Visual Studio 2013 the problem started.
A colleague is also running the same solution on his Windows 8.1. We share the solution using a git repository.
He has both VS 2102 and VS 2013 installed. He experiences the same problems in VS 2013, so he has started to use VS 2012 for this solution.
It runs fine in VS 2012. It is the same solution and same machine as it fails in VS 2013.
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.
I am new to visual studio 2010. I hav IE10 and visual studio 2010 and windows 7 32 bit OS.
while running the website I am getting error as "attaching the script debugger to process(5580) iexplorer.exe on machine is failed. a debugger is already attached"
I tried by running this in command prompt run as administrator
regsvr32.exe "%ProgramFiles%\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll"
but its not working for me.
how to solve this issue.
Please help me
I am new to visual studio 2010
thank you in advance
shubha
You may have some processes attached to the application pool worker process.
For instance, verify if you have installed and activated "Debug Diagnostic Tool" and uninstall it or just deactivate the rule.
After installing VS2012 RC on my dev PC, I keep getting this error on the splash screen on startup of the application, immediately after selecting the appropriate Environment Setting.
Unable to load DLL 'psapi.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
VS2010 threw this error immediately after the VS2012 threw the error. (VS2010 worked well prior to the 2012 Installation). Both applications now don't even work at all.
Things I've tried:
Tried running devenv with all the switch cmds of VS I know - /Resetsettings, /ResetSkipPkgs, /safemode
Uninstalling and installing ALL versions of VS on my PC (2008, 2010 and 2012) - after clearing the %temp% windows folder.
Formatted my PC and reinstalled all versions of VS again from the scratch.
PLEASE NOTE : The Visual Studio 2012 worked when I restarted my windows in Safe Mode.
My PC is a Lenovo i3, 4G RAM, 64Bit Windows 7.
Please help me as I have wasted days trying to solve this issue to no avail.
Thanks a lot.