• AB (21/21) Jul 07 2018 Hello, my software configuration is as follows:
• Rainer Schuetze (14/41) Jul 12 2018 Sorry for the inconvenience. Unfortunately, the uninstaller doesn't have...

AB <ab396356 users.sourceforge.net> writes:

Hello, my software configuration is as follows:

* Visual Studio Community 2017 15.7.4
* DMD v2.080.1
* Visual D v0.47.0

My problems:

1. Visual D kept crashing Visual Studio whenever I tried 
accessing the "Visual D" menu.
2. The uninstallation of VisualD is not complete: despite having 
uninstalled Visual D, its D options still litter Visual Studio 
(which, coincidentally, complains about the Visual D extension 
missing):

For example:
Tools -> Options... -> Projects and Solutions -> Visual D Settings
Tools -> Options... -> Text Editor -> D

I have taken the decision to not use Visual D, so only problem 
[2] is of importance to me.

I need guidance on how to clean up my Visual Studio installation, 
to remove all traces of Visual D, and to repair the corruption 
that its setup did to VS, preferably without a full 
reinstallation of VS.

Thank you.

Rainer Schuetze <r.sagitario gmx.de> writes:

On 07/07/2018 15:24, AB wrote:
 Hello, my software configuration is as follows:
 
 * Visual Studio Community 2017 15.7.4
 * DMD v2.080.1
 * Visual D v0.47.0
 
 My problems:
 
 1. Visual D kept crashing Visual Studio whenever I tried accessing the 
 "Visual D" menu.
 2. The uninstallation of VisualD is not complete: despite having 
 uninstalled Visual D, its D options still litter Visual Studio (which, 
 coincidentally, complains about the Visual D extension missing):
 
 For example:
 Tools -> Options... -> Projects and Solutions -> Visual D Settings
 Tools -> Options... -> Text Editor -> D
 
 I have taken the decision to not use Visual D, so only problem [2] is of 
 importance to me.
 
 I need guidance on how to clean up my Visual Studio installation, to 
 remove all traces of Visual D, and to repair the corruption that its 
 setup did to VS, preferably without a full reinstallation of VS.
 
 Thank you.
 

Sorry for the inconvenience. Unfortunately, the uninstaller doesn't have 
access to the private registry that is used by VS 2017.

I investigated this now, and it seems the corresponding action to what 
happens in VS2015 or earlier in the registry is to change the timestamp of

"c:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\Common7\IDE\Extensions\extensions.configurationchanged" 


As this is usually only modifiable by an administtrator, the easiest 
thing to do is copy it somewhere else, edit and resave it, and copy it 
it back.

Also delete this folder as the uninstaller fails to delete one file:

"c:\Program Files (x86)\Microsoft Visual 
Studio\2017\Community\Common7\IDE\Extensions\Rainer Schuetze"

I'll integrate this into the uninstaller...