Add ShellExtension README.md

flaviu22 · Mar 12, 2020 · 2b2d631 · 2b2d631
1 parent 5c5cfbc
commit 2b2d631
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 0 deletions.
diff --git a/Docs/Developers/README.md b/Docs/Developers/README.md
@@ -13,5 +13,6 @@ Developer documentation is in meant for people who want to compile WinMerge them
  * [User manual information](../Users/Manual/README.md) tells how to convert manual from DocBook to HTML and HTML help.
  * [Options](Options.html) explains WinMerge's options handling.
  * [Plugins](Plugins.html) contains documentation about plugins-system.
+ * [ShellExtension](../../ShellExtension/README.md) contains tipps for the Windows Explorer shell integration.
  * [InnoSetup](../../Installer/InnoSetup/README.md) contains documentation about WinMerge's installer.
  * [Unit testing](UnitTesting.html) instructions for unit testing in WinMerge development.
diff --git a/ShellExtension/README.md b/ShellExtension/README.md
@@ -0,0 +1,13 @@
+# Shell Extension
+
+Source code from the Windows Explorer shell integration.
+
+## Testing
+
+WinMerge sets executable path (`WinMergeU.exe`) which ShellExtension starts every time when options-dialog is closed. This can cause problems when testing several versions of WinMerge. There is registry value to overwrite path to WinMerge executable:
+
+```
+HKEY_CURRENT_USER\Software\Thingamahoochie\WinMerge\PriExecutable
+```
+
+It does not exist by default, so create `PriExecutable` as string value and type path of `WinMergeU.exe` you mainly use as its value. If this value exists ShellExtension does not care about another path value.