How to: Work with Stale Code
This topic applies to:
Visual Studio Edition |
Visual Basic |
C# |
C++ |
J# |
Express |
No |
No |
Yes |
No |
Standard |
No |
No |
Yes |
No |
Pro/Team |
No |
No |
Yes |
No |
In some cases, Edit and Continue cannot apply code changes to the executable immediately, but might be able to apply the code changes later if you continue debugging. This happens if you edit a function that calls the current function or if you add more than 64 bytes of new variables to a function on the call stack
In such cases, the debugger continues executing the original code (called stale code) until the changes can be applied. The stale code appears as a temporary source file window in a separate source window, with a title such as enc25.tmp. The edited source continues to appear in the original source window. If you try to edit the stale code, a warning message appears.
.gif) Note |
|---|
The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose Import and Export Settings on the Tools menu. For more information, see Visual Studio Settings. |
To enable or disable the stale code warning
On the Tools menu, click Options.
In the Options dialog box, select the Debugging folder.
In the Edit and Continue group, select or clear the Warn me about stale code check box.
Click OK.
See Also
Reference
Stale Code Warning Dialog Box
Edit and Continue, Debugging, Options Dialog Box