About how to efficient debug, there are two questions want to consult everybody,
1. When debugging code left hand press keyboard F10 or F11, right hand mouse, is a high efficient posture, bosses are how to debug,
2. Step, want to go to have a look at a variable under other classes, but when I come back again for half a day, how to face this situation?

CodePudding user response:

1 there is nothing wrong with this, I have been this pose,
2 this, I usually use monitoring and real-time output,

CodePudding user response:

Basic step is not tracking, the code is now separated,

You are debugging your things, single step, consider when multithreaded, when injection, when an asynchronous, when the reflection, when a message, when the response, this sort of thing is routine programming method, single step has no meaning,

So, upstairs said monitoring, trace this class is the important method, single step can only be local, debugging breakpoints have entered the local later, see if local execution sequence logical to use the

Want to go to have a look at a variable under other classes, Ctrl +, but doesn't make sense, we are only focusing on debugging to debug, within the scope of the execution, is the scope of the context, this context is either global, or is passed, so it is very rare basic leap to see what other classes

CodePudding user response:

On your second question, you said you can use a bookmark (bookmarks)

CodePudding user response:

Press the mouse button left foot and right hand, efficient not

CodePudding user response:

F12 turn to define, CTRL + - return on step is your second question

CodePudding user response:

First of all, to have such a dress

CodePudding user response:

CTRL + - navigate back you're worth it

CodePudding user response:

The right mouse button control breakpoints, vs toolbar directly "to" the next step, the left hand basic CTRL + c and CTRL + v

CodePudding user response:

Left hand, right hand a slow-motion

CodePudding user response:

Left hand, right hand slow-motion replay

CodePudding user response:

CodePudding user response:

refer to the original poster nangongxiaobai response:

about how efficient the debug, I've got two questions to ask you,
1. When debugging code left hand press keyboard F10 or F11, right hand mouse, is a high efficient posture, bosses are how to debug,
2. Step, want to go to have a look at a variable under other classes, but when I come back again for half a day, how to face this situation?

Right, step by step, after a long time will be better

CodePudding user response:

?? Ga ga ga ga ga

CodePudding user response:

No problem, no problem

CodePudding user response:

CodePudding user response:

Habit,,,

CodePudding user response:

CodePudding user response:

1. To help users to download software and data packets, the user needs to download many times, including software installation)
2. The user's computer runs slowly, as we have learned is very slow to run the test software have arranged for a new computer,
3. User testing software can not open,
4. Help users to install OVT light programming and letter 2.0, 3.0 light program
5. The user's computer is too card cannot daily work, memory chips, antivirus, clearing up the rubbish,
6. The user to replace computer need to backup data + configuration 263 enterprise email,

CodePudding user response:

Need to exercise the hand speed

CodePudding user response:

Left hand, right hand slow-motion replay

CodePudding user response:

1, I also am such
2, can use the navigation bar back, but I usually use "call stack" rapid return to I want to go to that a hierarchy of code see variables, including the return to the breakpoint,
View can also press F10, make yourself back,

CodePudding user response:

Grid clothes, backpack, plus a laptop this pose is good

CodePudding user response:

Have the function of a monitored variable, you can try

CodePudding user response:

When you touch the mouse your speed has been slowed down

CodePudding user response:

Left hand, right hand a slow motion, with his hands on both sides

CodePudding user response:

Please see dotnet code debug method

CodePudding user response:

Thought you were going to discuss the old man cart

CodePudding user response:

All love, old driver all understand

CodePudding user response:

CTRL + c CTRL + v? .

CodePudding user response:

Code the posture of ten million kinds of I like the most common way

CodePudding user response:

Is directly copy + c

CodePudding user response:

F11 single-step debugging, facilitate you screening program error, f10 by debugging process, to facilitate your search method, the two shortcut function is very nice, please according to the actual demand for corresponding operation,

CodePudding user response:

Grid clothes, backpack, plus a laptop this pose is good

CodePudding user response:

Basic step is not tracking, the code is now separated,

You are debugging your things, single step, consider when multithreaded, when injection, when an asynchronous, when the reflection, when a message, when the response, this sort of thing is routine programming method, single step has no meaning,

So, upstairs said monitoring, trace this class is the important method, single step can only be local, debugging breakpoints have entered the local later, see if local execution sequence logical to use the

Want to go to have a look at a variable under other classes, Ctrl +, but doesn't make sense, we are only focusing on debugging to debug, within the scope of the execution, is the scope of the context, this context is either global, or is passed, so it is very rare basic leap to see what other classes

CodePudding user response:

Basic step is not tracking, the code is now separated,

You are debugging your things, step into, when an asynchronous, when the reflection, when a message, when the response, this sort of thing is routine programming method, single step has no meaning,

So, upstairs said to monitor, trace this class is one step can only be local, debugging breakpoints have entered the local later, see if local execution sequence logical to use the

Want to go to have a look at a variable under other classes, Ctrl +, but doesn't make sense, we are only focusing on debugging to debug, within the scope of the execution, is the scope of the context, this context is either global, or is passed, so it is very rare basic leap to see what other classes

CodePudding user response:

In the next line of single step again a breakpoint, single step debugging F5 directly after come back,

CodePudding user response:

+ 1 ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

CodePudding user response:

Alt + F4nullnullnullnullnullnullnullnullnullnullnullnull