Debugging dotPeek Debugging a third-party .dll

Question

I am using dotPeek v1.2 with VS2013 Update 3 to try and debug C # .dll reference code. I followed all the instructions from the following tutorial: Using dotPeek as a Symbol server ( http://localhost:33417/ set as the location of the character, etc.). Honestly, I read a bunch of articles such as this and this , comb through all the necessary settings and really did not see 1 working solution for debugging a third-party non-structural DLL, so I'm not sure if this is a fully working product from this aspect.

Regardelss, dotPeek should be enabled as soon as the symbol server starts to enter and debug code from third-party assemblies from VSNET in accordance with their documentation. I know which .dlls to choose for dotPeek because I checked their path from Debug -> Windows -> Modules.

I also have ReSharper installed, which allows me to decompile when I right-click on a line of code and select "Go to declaration". The problem is that the character server does nothing to help maintain the code during debugging. Rather, the decompiled source provided by ReSharper seems like VS.NET wants to jump over. The problem is that I always get the following error:

Source file: C: \ Users \ username \ AppData \ Local \ JetBrains \ ReSharper \ v8.2 \ SolutionCaches_ReSharper.Meijer.Ecommerce.Nav.WebAppServices.-382002776 \ Decompiler \ decompiler \ 53 \ 66e7ccc2 \ MyClass.cs

Module: C: \ Projects \ MyProject \ bin \ Debug

Process: [24808] vstest.executionengine.x86.exe

The source file is different from when the module was created. Could you use it anyway as a debugger?

If I say yes and the step in the debugger seems to be in lines that do not exist in the file and are not synchronized. This makes sense because it shows the .cs class from the "Source file" location, but has the .dll loaded from /bin/Debug

However, I don’t understand why this is happening anyway, since dotPeek should serve the downloaded characters from /bin/Debug and not try to enter any decompiled ReSharper source.

How do I configure VS2103 actually debug characters and code submitted with dotPeek ?

Answer 1

One big question is that you need to make sure that you have a valid path for the cache directory on the Tools → Options → Debug → Symbols page.

In addition, on the debugging options main page (Tools → Options → Debugging → General), make sure that you:

• Uncheck "Include only my code"
• Uncheck the "Enable .NET Framework Initial Step"
• Check the box next to "Enable server support."
• Uncheck "Require source files to match original version

It is also worth checking the "diagnostic messages of the print source server to the output window" and checking the output window when trying to enter third-party code. We hope that this will mean any problems.

This is how I set up the settings and I can debug third-party DLLs (obviously dotPeek must have a .dll loaded in the build explorer before you start debugging).