Obviously open your project with the correct source for your release build. In the Tools Options dialog, select the Debugging parent node in the dialog and then select Symbols or ofcourse just type Symbols into the search text box in Visual Studio Now press the folder button and type in the location of your PDB files folder. Now attach the debugger to your release build and Visual Studio will as mentioned locate the correct symbols and attach them and then allow you to step through your source.
See Specify Symbol. So what are. PDB files? Please rate your experience Yes No. Any additional feedback? Important The debugger will load only a. Generate symbol files for a C or ASP.
NET Core project. NET only For detailed information on project settings for debug configurations in C , see Project settings for a C debug configuration. In Solution Explorer, right-click the project and choose Properties. Build your project. Submit and view feedback for This product This page. View all page feedback. In this article. Just kidding! For example, many local variables disappear because instead of putting them on the stack, as what happens in debug builds, the code generator puts them in registers instead.
Additionally, release builds aggressively inline calls to functions so the code generator puts the body of the function directly in the calling method. The switches I will show you have nothing to do with optimizations and PDB file creation does not affect optimizations. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow.
No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical.
0コメント