Good morning,
I deleted the "path" environment variable and now I´m not able to open Visual Studio. I tried most of the solutions that have been commented in other threads, but most of them are based on a sistem recovery, which I didn´t have configured.
Most of the programms keep working, but I have problems with Visual Studio. I tried to reinstall it, but it still doesn´t work. I would like to know which are the "path"-s that Visual Studio needs to work in order to recover it.
I use Windows 10.
I have enabled Just My Code in the debugging options, but it says it's for managed only.
When I have the debugger in the managed mode, it runs but closes straight after and I can't step into each line of code.
How can I make it work?
When Just My Code is enabled, it is possible to choose Break on the Debug menu and stop execution at a location where there is no My Code to display. When that happens, no code is displayed. Additionally, if you choose a Step command, it will take you to the next line of My Code.
First try to read How to: Step Into Just My Code and then will understand what they do.
As you're saying that debugger is not running, there might be many reasons:
You could type Devenv.exe /SafeMode, which starts Visual Studio in safe mode, loading only the default environment and services.
If it does not work, you could type Devenv.exe /resetsettings. It restores Visual Studio to default settings. Optionally, reset the settings to the specified .vssettings file.
More information about the Devenv.exe command line.
Switch other accounts or create a new account and try it again.
If it doesn’t work still, please uninstall Visual Studio via Add/Remove Program thoroughly and reinstall it again.
In Visual Studio 2010, I'm adding a command by going tools -> customize -> commands. However, the changes I make there appear to be temporary. After I open Visual Studio another time, my command is not there.
How do I add a command so that it stays?
The problem probably comes from VS not having permissions to modify its settings, when running as a non-administrator, due to UAC limitations. I actually don't have this problem - on my Win7, VS10 settings stick even when running as regular user, but this might be an issue with specific installation settings.
Bottom line, running VS as administrator should remove the permissions limitations, and allow VS to store the modified settings properly.
Strange Visual Studio (TS 2008) problem: The IDE completely freezes whenever I switch from Release to Debug mode in a specific project. It happens right as I switch, before I try to build or do anything else.
The whole thing started out of the blue, without any abnormal change I can think of.
I tried to clean the solution, but it didn't help.
Anyone ran into this before?
If everything has worked fine and then stopped, usually it means there was some problem even though it had passed unnoticed.
Things I would try one after another:
Check which files were changed (why and how) after update from a source control engine
Review the list of extensions and plugins. Try to disable all or some of them
Close Visual Studio and kill all the development processes: devenv, mspdbsrv, vcpkgsrv, msbuild, msvsmon, vshub, vstest etc
Remove .suo, .ncb, .VC.db, .VC.VC.opendb files of the solution as well as .vs directory, which sometimes cause problems
Remove project setting files, sort of YourProjectName.vcproj.DOMAINNAME.LOGINNAME.user or YourProjectName.csproj.user. The setting file name depends on a project kind you use
Run "C:\Program Files\Microsoft Visual Studio [vs_version]\Common7\IDE\devenv.exe" /setup or "C:\Program Files (x86)\Microsoft Visual Studio [vs_version]\Common7\IDE\devenv.exe" /setup for x64 environment
In some complex cases, it helps to remove user settings, located in home %USERPROFILE%\AppData\[Local|Roaming]\Microsoft\VisualStudio[vs_version] and in registry HKCU\SOFTWARE\Microsoft\VisualStudio[vs_version]
It should reset all things to the beginning state. If it won't work, so there are additional tools to investigate. Download Process Explorer and once IDE freezes, start the Process Explorer, find the devenv process, double-click on it and go to Threads tab. Check, which thread has the biggest switch delta in case of the freeze, double-click on it and take the name (or offset) of the top function. It gives additional info where the problem may be.
Moreover, sometimes it helps to repair Visual Studio in the "Add or Remove Programs" wizard in Control Panel.
Had this problem in 2017. I ran VS 2017 as Administrator and it worked.
I've encountered this in VS 2017 (15.8). Upgrade to the newest version (15.9 at that time) resolved the issue.
VS seems to be doing a lot behind the scenes and putting project-specific files in App Data and who knows where else. I had this experience: I had a project which had two sets of identical code in two different directories: one for production, one for development. The development project started hanging on debug, the production did not. Tried all kind of settings and deleting .suo files, but no help. So I renamed the directory that the development version was in and presto, eveything worked without hanging.
In my particular case, I tried many other answers with no luck. It turned out that a call to this was hanging the debugger:
Log4NetExtensions.AssertFail("Error");
I managed to narrow it down to this line of code by bring up the threads window under [ Debug > Windows > Threads ] and clicking on the current thread to browse to the line of code it was hanging on.
Newly created environment variables are not passed on to visual studio sometimes. What may be the problem? The environment variables are not visible to VS even when I close and restart it. This is an intermittent problem and thus hard to diagnose.
Environment variables are passed on to child processes from their parent process so if you used explorer to change the environment variables and also launch visual studio then the environment vars should be visible to VS.
But if you are using a third party application launcher (like launchy) then the changes may not be propagated if the launcher does not receive and act on the windows WM_SETTINGSCHANGED event.
So you may try one of the following...
Launch VS from explorer
Restart the app launcher and launch VS from it.