Bug #87871 MySQL for Visual Studio 1.2.7 will not uninstall

• Submitted: 26 Sep 2017 14:07
• Modified: 27 Sep 2017 5:27
• Reporter: d karres
• Status: Duplicate
• Category: MySQL Visual Studio Integration
• Severity: S2 (Serious)
• Version: 1.2.7
• OS: Windows (Windows 10)
• CPU Architecture: Any
• Tags: MySQL, Visual Studio, Windows 10

[26 Sep 2017 14:07] d karres

Description:
I recently downloaded and installed MySQL for Visual Studio 1.2.7.  I first uninstalled the previous version though i don't recall the rev number.  

When doing the install step for 1.2.7 I was never given the option to "install" only change, repair or remove.  I figured it knew it business so i selected "change" and it seemed to install.  Visual Studio had no clue about anything to do with MySQL though.

I went back to the installer an tried "repair"; it brought up the various GUI progress bars but nothing actually changed as far as i can tell.  I tried "Remove" (from the installer) with the same results.  I tried remove from the Windows Control Panel, nothing.

I made sure all VS related everything was off and tried the steps above, nothing.

I rebooted and tried the removal steps, nothing.

Googling found a suggestion of removing the MforVS install dir.  Jeepers! that was a struggle.  Even the windows admin account couldn't just delete that dir.  The group admin came in and did some magic invloving the windows commandline command "takeown".  Once the install dir was gone I rebooted to be safe.

After reboot I tried to reinstall MforVS but all the same stuff happened with the end result of I have no working MforVS.

Oh, I read the doc comment about MforVS not wanteing to live next to Connector.Net.  I removed that too in the processes above.  No joy.

How to repeat:
unknown

[26 Sep 2017 15:00] d karres

Output from MsQL Community Installer attempt to remove MforVS 1.2.7

Attachment: MforVS.txt (text/plain), 40.76 KiB.

[27 Sep 2017 5:27] Chiranjeevi Battula

Hello karres,

Thank you for the bug report.
This is most likely duplicate of Bug #71329, please see Bug #71329

Thanks,
Chiranjeevi.