[Issue 17355] Path to lib64 and $(DMDInstallDir) not correct

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=17355

--- Comment #4 from Rainer Schuetze <r.sagitario at gmx.de> ---
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\VisualD

is where the installer remembers the setting made during installation. For each
Visual Studio version that you choose for Vsiual D installation, it is also set
at

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\<VS-Version>\ToolsOptionsPages\Projects\Visual
D Settings

When starting VS, it copies these settings to the user hive:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\<VS-Version>_Config\ToolsOptionsPages\Projects\Visual
D Settings

If you change any global option for Visual D it saves all of them (including
DMDInstallDir) to

HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\<VS-Version>\ToolsOptionsPages\Projects\Visual
D Settings

Please note that the last two registry keys are defined by VS and passed to
Visual D. To start from scratch, you need to cleanup the latter.

For VS 2017 these registry hives are mapped into a "private" registry that you
can only edit with regedit using "Load hive". So there is little the installer
can do to cleanup the settings.

The extra step writing the installer value into the VS registry seems
gratuitous, though, and might be actually causing the problems for VS2017.
Reading the default from the Visual D installer key should be better.

--