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.
Related
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 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?
Is there any way to avoid the window of development server? (Not stopping or avoiding to run the development server, just the window).
In Visual Studio 2010 (and before) it only appears when the development server was started. Now, in Visual Studio 2012 it is opened each time the project start, no matter if the development server has already started and you have closed it.
I've found that I can run projects using IIS Express. Also it will make our lives easier when we want to be able to access to the project running from other PC.
With Visual Studio 2012 it comes already installed (in fact is the default setting for projects started in it). With Visual Studio 2010 it can be installed (see post).
I have about four web projects that I am hosting in IIS Express. Whenever I do a build in Visual Studio 2010, the build will be blocked until I manually kill IIS Express. The build then completes. A new instance of IIS Express is created that works as expected.
I tried to do a prebuild event to kill IIS Express with taskkill, but the lock up seems to happen before the prebuild event is executed :/
If I stop the hosted sites, Visual Studio 2010 will also build as normal.
From research, one possibility is IIS Express is trying to display a dialog that Visual Studio 2010 is waiting for the user to interact with, but doesn't actually display the dialog.
Has anyone else had an issue with IIS Express and Visual Studio 2010 locking up on building? Or some insight on how to debug this issue?
If i remember correct the last service pack for vs 2010 corrected that error (at least on my maschine).
Sounds like visual studio is trying to do something on port 80, which IIS is blocking ( thats the default listener port for it ).
A simple google search of port 80 visual studio brings up several promising hits ( how to configure it, and hey! 2nd one even has a fix for a similar problem. )
This happens to me constantly, but then again I'm using WinXP / VS2010 / IIS Express 7.5. I suspect the WinXP part is the culprit, perhaps a bug for this particular scenario? At any rate, VS2010 wants to rebuild one of my web apps, but appears to wait indefinitely on some files in the Temporary ASP.net directory for the web app, until I stop IIS Express.
Mostly it happens if we open a team project from tfs 2008 or tfs 2010, but crashes can happen any time.
When VS is closing down, it crashes nearly every time.
Tried trial RTM and our MSDN download - same story. Tried on three different PCs - same issue. Tried on 32 and 64-bit Windows 7 and Windows Server 2008 R2 - crashes.
Is it just our luck or does it happen to you to?
Here are some tips that will hopefully help you identify the problem:
http://blogs.msdn.com/kirillosenkov/archive/2010/02/08/how-to-investigate-and-report-visual-studio-issues.aspx
Ideally, get a call stack of the devenv.exe main thread with symbols loaded, and post it here (or even better), attach to the Connect bug. From the stack we'll likely be able to tell what kind of problem it is.
I logged it as an issue on Microsoft Connect.
There is a new release of the TFS Power Tools and Visual Studio 2010 Productivity Power Tools which seem to reduce the instances of VS crashing (although it still seems to crash from time to time). It might be worth checking out if you use either add-in.
Apparently, the crash was caused by using a DNS name in Connect to Team Foundation Server.
I replaced that with the IP address of the TFS server and the crashes went away.
We have two Windows Server 2003 DNS servers, and it looks like Visual Studio 2010 does not communicate with them correctly. Visual Studio 2008 connects to the TFS without any issues.
Apparently, there a bug:
"Large Visual Basic project crashes when closed"
http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=29797