Pictured above, VS2019, code can literally change during the process of operation, the original is in the breakpoint to change, now literally changed directly, the key is the modified code again not to perform, debugging very nausea,
After change will only use the green wavy lines marked, how to disable this, back to the original appearance, into the breakpoint to debug?

CodePudding user response:

This state of edit and continue to have been checked, also cancelled check tested again, it doesn't work

CodePudding user response:

VS2019 is installed very early, no problem, recently updated version after 16.4.2, he realized the problem

CodePudding user response:

Consult! You have know? Again did not find item set

CodePudding user response:

If used WPF xaml development, will find that use vs2019Debug mode, change the xaml elements automatically mapping changes to the interface,
This should be 19 new features, you need to set up a property to control,

CodePudding user response:

Ok, thank you moderator, the key in the c # development would be a little not adapt, even in the debugging method that can be directly to create a new reference although breakpoint will walk that way, after but not actually inside the code execution, it is a bit misleading programmers mean, thought he wrote in the right way,
I look again carefully, look have the relevant Settings, to give you said

CodePudding user response:

Can modify the code when debugging is it cow force, VS2010 version before no,

CodePudding user response:

Debug the new methods, not into the breakpoint can't write the code

CodePudding user response:

I also want to change anytime and anywhere,
But my side set, for nothing,
When debugging, still can't literally change,

CodePudding user response:

I also think this update very vexed, I just don't want to debug the code can be modified, so as to avoid code change by mistake,
I find VS update fast Bug too much, now I often press the delete key delete things is not where the cursor as a result, only the back and restore them to recovery,

CodePudding user response:

Above a few places, please see the dry, VS2019 16.4.2 version,
First, the runtime code literally change, need not can literally change into the breakpoint, attention is literally change: no matter the method, variable, can add comments can edit, don't interrupt point in debug state,
Second, literally change very affect debugging, enter the breakpoint debugging status to modify the code as well as the original can change the test again, but not into the breakpoint to modify the code, after entering the breakpoint debugging state won't take effect, this is very affect the work, at least for now it's easy to debug code appear misunderstanding, may have to adapt to a period of time, adjust the work habits

CodePudding user response:

reference 4 floor exception92 response:

if used WPF xaml development, will find that use vs2019Debug mode, change the xaml elements automatically mapping changes to the interface,
This should be 19 new features, you need to set up a property to control,

Thank you, old, should be a new version of the feature

CodePudding user response:

references to the tenth floor yangxxlong response:

the above a few places, please see the dry, VS2019 16.4.2 version,
First, the runtime code literally change, need not can literally change into the breakpoint, attention is literally change: no matter the method, variable, can add comments can edit, don't interrupt point in debug state,
Second, literally change very affect debugging, enter the breakpoint debugging status to modify the code as well as the original can change the test again, but not into the breakpoint to modify the code, after entering the breakpoint debugging state won't take effect, this is very affect the work, at least for now it's easy to debug code appear misunderstanding, may have to adapt to a period of time, adjust the work habits

I say is you this kind of situation,