I am having trouble with Visual Studio 2012. We have windows service written in VB.NET and we have one unit test we use to initiate debugging process for that service. Problem is that sometimes Visual Studio detaches from debugging of service and instead of breaking execution, service just continues execution until everything is done.
How to prevent this form happening? It's very annoying and destroys prepared test cases.
Solution is to install Visual Studio 2013 with Update 5.
Also to note, release version of VS2013 has a bug which is causing application rebuild every time you try to run/debug application (even though you didn't change anything).
Related
I have Visual Studio 2015 version 14.0.25420.01 update 3.
When i start my program from the environment with local debugger and after that try to make a change in the code, most of the times visual studio crashes, and in some i don't see the changes and the keyboard is not responding anymore.
If Visual-studio doesn't crash, i can fix the non-responding keyboard issue by closing and opening the project again, it allows me to continue my work. This problem happen on every project that i am trying to work on, so code doesn't really matter here. I also have earlier versions of Visual Studio and they work fine without this issue. Any ideas?
To be clear: Visual Studio crashes only when i edit my code while running it.
Since a couple of weeks, MSBuild doesn't finish any builds anymore when I try to build a Visual C++ project in Visual Studio 2010.
In Process Explorer I can see that a subprocess MSBuild.exe is attached to devenv.exe, but no cl.exe is ever invoked. After 30 seconds another MSBuild.exe subprocess is attached and this continues for a while, until finally the build is aborted (or I kill Visual Studio).
I observed that after killing Visual Studio, the MSBuild processes are orphaned and if I restart Visual Studio and invoke another build, it suddenly works.
When every orphaned MSBuild process has exited, I cannot build anymore.
I tried to check, if there's anything wrong with the MSBuild installations, but at first sight it looks fine.
I reinstalled the SP1 of VS 2010 as well as Windows SDK 8.1, but nothing changed.
I also installed VS 2015 Express, which now ships with MSBuild (previously was shipped with .Net Framework), but same behavior.
The problem occurrs with different Visual C++ projects.
I could not google any solution, for slightly related problems there seemed to be issues with Avast antivirus. This is a corporate notebook, which is protected by Sophos, so I can't change any antivirus settings.
EDIT1
If I invoke MSBuild directly with
c:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe .\MyProj\MyProj.vcxproj
it just works.
Any hints or suggestions?
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.
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 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.