I've recently switched from Visual Studio 2017 to 2019 and I'm having an issue with changing the code after hitting a breakpoint (Debugging).
Even a small change, e.g. changing the value of a variable prevents the code from continuing and I always get the message:
Edits were made to the code which cannot be applied while debugging.
Visual Studio 2019 Debugging settings
Is this a bug of Visual Studio 2019 or is this an expected behavior? On VS2017 I was able to change large portion of the code and still I was able to continue executing the code without restarting the app.
Here's the full, up-to-date list of where edit and continue works, and doesn't work.
https://github.com/dotnet/roslyn/blob/main/docs/wiki/EnC-Supported-Edits.md
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.
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.
My Visual Studio stopped recognizing external file changes.
I checked the respective options being enabled ('Environment/Documents/Detect when file is changed outside the environment' and 'Environment/Documents/Auto-load changes, if saved).
I restarted Visual Studio as well as my machine.
I tested other software that recognized changes, such as Notepad++, which works just fine.
I tested different Visual Studio projects to check if it has something to do with the project being screwed up somehow - same effect in all projects I tested.
What's going on here?
(There are some SO questions that appear to be related judging by the headline: VS2012 not detecting external changes, Visual Studio 2012 stopped applying changes to solution and Visual Studio 2012 not detecting file change, but all are about different issues.).
Happened to me as well this morning. Exiting VS and relaunching/opening the project seems to have it working again. Super strange!
I apologize as this may seem as bit of a general question.
I have developed a couple of VB programs using Visual Studio 2010 Professional and others on Visual Studio 2013 Ultimate. While I have not done any work in about a month with either version of Visual Studio, I thought I would go in and start work on a new project.
After entering some code in Visual Studio 2010 using WinForms, I found I was unable to run the code in the debugger (pressed the start button and F5).
It acted like it would start, then it just stopped and returned back to my code.
I thought I would try it on another program that was completed and working a couple of months ago, but I had the same issue present itself. Attempting to use Visual Studio 2013 had the same effect.
Any ideas from anyone? Has anyone else experienced this same issue recently? Once again, I do apologize for the lack of examples here, but I'm not sure what I can include to show the problem.
IMO, you should try resetting visual studio settings (and a restart may solve the issue)
you can try following
do it via visual studio -> tools -> import export settings
or you can run this command devenv /resetuserdata
or checkout this http://msdn.microsoft.com/en-us/library/ms241273.aspx
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.