Debugger Settings Change Between Visual Studio Instances - visual-studio-2010

I having the most annoying problem with Visual Studio 2012 settings. Every time I close and re-open Visual Studio I find the Just My Code debugger setting disabled. No matter how many times I enable it, it is always disabled the next time I open the IDE.
Any idea how this could be occurring? All the other settings seem to persist well. It's only the Just My Code setting that's changing.

Well, I found the problem.
I have the .NET Reflector Plug-In installed in Visual Studio and it apparently doesn't like "Just My Code" so it disables it on start up.

Related

Visual Studio 2015 crashes while running a program and editing code

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.

Visual Studio crashes when locking computer or starting another instance

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.

Visual Studio: Disable Auto Copy text on doubleclicking inside of it

I don't know how this was turned on, when I double click inside a word it's auto copied to the clipboard in the Visual Studio IDE (it occurs with ANY filetype).
I looked through options for Resharper and Visual Studio and found nothing that adresses it.
Any insight? The only plugin I use is resharper and I suspended it but no dice.
Is it happening in visual studio only or in other programs also?
Try it in notepad. If it is happening in notepad also then there might be some other software which is causing this.

Logs for Visual Studio Shutdown error?

Every time I close visual studio it tells me that there has been an error.
Eventually it tries to restart visual studio. This only happens when I close Visual Studio. To have it reopen visual studio after I just closed it is a bit frustrating.
Is there a log I can go look at to see what is causing the failure? (I have a few addins installed. And I am hoping that I don't have to uninstall them one by one to see which is causing this issue.)
If it's trying to restart itself, something should show up in the Windows/Applications event log in the Administrative Tools list.

Visual Studio Option hangs

Have anyone experience a problem when you click OK button in Visual Studio 2010, VS would hangs? VS used 100% of cpu power of one of cores. Event I didn't change any setting and click OK, it would still run into this issue.
I imported the default "Visual C# Development Settings" (.vssettings) and it fixed the issue.

Resources