It seems that, since this afternoon, the VS2010 debugger will occasionally start checking for a CD when started. It produces a dialog box that I have to cancel several times before finally being able to close the editor and restart it. Two or three hours pass and the problem returns.
So, aside from reinstalling everything, what else could I do?
Found that something weird happened when I installed VS2012 RC. Removing VS2102 and reinstalling VS2010 solves the problem.
Related
I use Visual Studio Community 2019 with C++ (no .Net). Yesterday I updated to version 16.7.1. Ever since then, Visual Studio hangs on exit at the step "Unloading Projects". No projects are unloaded, and the progress bar never starts moving. The program simply hangs and is unresponsive. The only way out is to kill the process.
It also hangs whenever I try to change the Configuration target for the solution. Both issues occur on any of my solutions that I open. I have tried using Visual Studio Installer to repair the install, but it makes no difference. The installer does report one issue: Couldn't repair Microsoft.AspNetCore.TargetingPack.3.1.3.1.3 But this hardly seems like it matters to my Win32 projects.
This problem definitely started as soon as I updated to 16.7.1. I don't recall the previous version I had, but I had just updated a few days before so it was probably 16.7. I am posting to see if others have this problem and if anyone has found a solution (other than falling back a version). I will limp along with it for now.
Same happened to me. Just use visual studio 2017. Only thing that fixed it for me.
So, I was using Visual Studio 2013, it crashed, and when I restarted it the Search Solution Explorer had stopped functioning correctly:
It fails to find any file if you type in the exact file name
It fails to find any static files e.g. HTML, CSS, JavaScript, etc.
It fails to find any configuration files e.g. Web.config
It seems to still find some files on a partial match, but not all files that you'd expect it to match e.g. if I search for Account I'd expect it to find AccountController.cs and AccountControllerTest.cs but it only finds the latter.
Some further info:
If I start VS 2013 in safe mode Search Solution Explorer works fine without any problems
If I manually disable or uninstall the extensions I'm using and start VS normally, the problem with Search Solution Explorer reappears
Has anyone come across anything similar to this, or got any suggestions of what to try to get Search Solution Explorer working again?
Update
I've had some joy running devenv /ResetSkipPkgs and devenv /ResetSettings. After a I ran those command Search Solution Explorer started working again, and works most of the time now. It still fails occasionally. Sometimes restarting Visual Studio will get it working again, but sometimes it just plain refuses to find certain files that are there.
Update 2
I installed Visual Studio 2013 Update 2, and Search Solution Explorer ran without any problems for just over a week before this problem reappeared. Restarting Visual Studio got Search Solution Explorer working again.
I was able to narrow this down to the extensions I was using, "Productivity Power Tools 2013" seems to break the search feature for me in IIS, so I've disabled it for now. I'm getting a full set of results when searching now.
I came to this conclusion by uninstalling all of my extensions and reinstalling them one by one until the problem reappeared.
A coworker also had some success with this solution, launching DevEnv.exe with /ResetSkipPkgs
http://msdn.microsoft.com/en-us/library/ms241276.aspx
Update
The problem returned for me after about 30 minutes, no specific cause noted. It was nice while it lasted. Removing all extensions gets me the same behavior as OP, only running in safe mode appears to work.
Deleting the .suo file also seems to fix the problem for a while, and then it comes back. I'm about to resort to a reinstall of vs2012 just to get this search feature back.
Please try to install VS2013 update 2 CTP before reinstalling everything and see if it fix the bug:
Weird that it works in Safe Mode, or that you manage to fix by removing extensiosn and it then re-appears...
but if some of your projects are in solution folders, then there is a known bug, fixed but not released yet apparently:
http://connect.microsoft.com/VisualStudio/feedback/details/801836/solution-explorer-doesnt-search-files-projects-inside-solution-folders
I have the same issue and confirmed it related to VS2013 Update 2 RC. Uninstall it will fixed this issue.
Wait for GM version of VS 2013 update 2.
I still had this issue both prior to and after installing VS update 3. I should note that it went away after I installed that for a while, and then came back. I suspect (but cannot confirm) that the broken behavior's return coincided with a lockup of my system which necessitated a reboot...
Anyway, I had the Productivity Power Tools installed, and after reading the answers here wondered if it might be complicit, and so I went to disable it and noticed it had a pending update. I went ahead and updated the add-on, and that resolved the issue for me (again). We'll see if it stays fixed.
This may caused by other extensions you have installed in your visual studio. I have some issue, found out Telerik JustTrace caused this issue.
Running devenv /ResetSkipPkgs will fix the problem but, as noted, it will return. For a permanent solution, add this parameter to the target in the exe's properties:
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe" -ResetSkipPkgs
My Visual Studio crashes each time I try to debug my ASP.net application.
I've been working on this application for months and only now has this issue come up. I've tried rebooting to no avail.
When I press F5, Visual Studio immediately freezes up and displays no error message. I also get the exact same behavior when I use the "Attach to Process" option to start the debugger.
The problem happens only with a particular application I'm working on. If I create a new project, I can debug that project, but as soon as I open up my original project, it's the same story all over again.
Also, I should point out that the "development server" icons appear in the System tray and do not disappear after the frozen Visual Studio 2008 is terminated.
Has anyone else encountered this?
I had the sysadmin re-install VS2k8 for me. That fixed the problem.
For some odd reason, the uninstall process took a very long time that surprised even the sysadmin who uninstalled and reinstalled it for me. I wonder if that could have anything to do with the problem.
Anyhow, the reinstall got me up and running again.
I'm trying to run the Visual Studio 2005 sample macro that attaches the debugger to calc.exe. Neither it nor any other macro seem to do anything when I run them. Calc.exe is running. "Tools->Options->Add-in/Macros Security->Allow macros to run" is checked. The error list shows no errors.
I had this same problem just happen to me. Macros in VS2005 were working fine, and then suddenly stopped one day. I checked permissions, that macros were enabled, etc. I ran the VS2005 setup program and repaired my installation, and none of this fixed it. Finally I uninstalled all the Windows updates that came in the last update cycle. This fixed the problem for me. I uninstalled a bunch at once, so I don't know exactly which update caused the problem, but I know it was at least one of these:
KB2916036
KB2912390
KB2911501
KB2909921
KB2909210
KB2901112
KB2898857
KB2862973
KB2843630
as I uninstalled all of these, and then the macros started working again. All of these Windows updates happened for me on Feb 13, 2014.
Hope this helps someone else.
Mark
P.S. I later discovered it was KB2898857 and you can leave it installed if you edit a few config files, as described here:
http://visualstudioextensions.vlasovstudio.com/2014/02/13/visual-studio-2010-macros-stop-working-after-february-2014-windows-update/#Update
Sounds like your Visual Studio 2005 instance is flaky, or that your Visual Studio 2005 installation is broken. If restarting VS2005 doesn't help, run the VS2005 setup and choose repair. Hope this helps.
Regards,
Sebastiaan
I had this problem too (but in Visual studio 2010).
After multiple attempts to fix it. I discovered it was a stupid problem.
I had another macro in another module that didn't compile (I had semi-colons at the end of lines).
Even though I was running a macro in a different module it didn't seam to matter.
If you are having this problem an easy thing you can check is looking in the error list for any errors in your code. It's very easy to put semi-colons at the end of your lines out of habit.
When I press F5, everything compiles fine, but when the app is to be started, VS crashes, showing the "Just in time debugger" dialog.
More than one (similar) solution has this problem. A new solution containing just a form, works. This problem started out of the blue, I have made no changes to the environment as far as I can understand.
I can start the app without debugging (ctrl+F5), and then attach the debugger.
I'm using VS 2008 sp 1.
Never seen this issue, have you tried turning off all your plug-ins like reSharper, CodeRush, etc.?
Update: When worst comes to worst I usually try this command line.
devenv.exe /ResetSettings
devenv.exe /ResetSkipPkgs
devenv.exe /Setup
try all these you can do them all at once or do them individually it is up to you. But be aware that you will be deleting all your settings that you have customized in to Visual Studio, so you may want to back them up.
The last thing you can try is this, to see if the problem is with something weird that is running.
devenv.exe /SafeMode
Starts Visual Studio in safe mode, and loads only the default environment and services, and shipped versions of third-party packages.
I've found the problem now. I had "Step framework source" enabled, which somehow broke the debugger (strange though, because it usually works). Turning that off, made me debug as usual again.
If you have undocked windows in debug layout search KB960075 on code.msdn.microsoft.com (can't add hrefs).
Do you have CLI.exe error issues? Check your event log. I've had the same issue and simply re-staged my machine out of panic since I was so near a deadline. I assumed that it was an issue with the registry and couldn't find an answer.
try repair or reinstall, don't waste time findin' the reason of the problem
I had the same problem, out of the blue the IDE would crash when I started to debug. Happened with any existing project that I opened, even the visual studio samples. I created a new project, just a blank dialog, ran it, and all was good. After that, the problem went away and I was able to debug again.
This happened to me just now, after my computer rebooted itself last night. When I was pressing F5 the app started but instantly shut down and the VS IDE crashed.
To fix it: Debug->Delete All Breakpoints. It worked for me.