More practical way of doing shell debug.
Trying to work on #3183 (closed), I've spend large amount of time trying to figure out how to debug the dll loading. Debugging involve hacking into registry that is only documented as code.
I think this is a bit to high of a ramp-up step. This is a proposal to reduce that a bit.
It mainly consist of a few line of documentation, and a helper command to run a fake Save Dialog, which in turn loads our custom menu.
Merge request reports
Activity
76 76 77 77 For optimized debugging copy TGitNatVis.dll and TortoiseGit.natvis from contrib\NatVis to %USERPROFILE%\Documents\Visual Studio 2017\Visualizers. 78 78 Then CGitHash will provide a readable preview of the SHA-1 and CTGitPath is also optimized. 79 80 81 Debugging the Shell Extension 82 ----------------------------- 83 Shell Extension can be tricky to work-on as it involves building and rebuilding a library that can be loaded (and thus locked) by Explorer.exe or any app using e.g. standard load save dialogs. 84 85 TortoiseGitStub(32).dll can choose which dllto load in which context. 86 When using a debugger, it will load the dll that is stored in the same directory as the process under debug. 87 88 Debugging Shell Extension works from a standard installation of TortoiseGit (use the standard installer to properly install all required registry keys form shell extensions) 89 90 * Write 1 to HKEY_LOCAL_MACHINE\SOFTWARE\TortoiseGit\ShellDebug (you need to be priviledged to do that)
Please register or sign in to reply