InstallShield 12 uninstall breaks TestDriven.NET

Published 10-02-2006 10:48 PM | jokiz
I have just uninstalled my Evaluation copy of InstallShield 12 which I used to setup our build server.  Unluckily, my TestDriven.NET addin suddenly is not behaving properly.  My officemate who also had his IS12 copy uninstalled currently have the same problem.

After doing an ad hoc run tests (right-click -> run tests), Visual Studio switches its output window to a test console output but no tests are run.  The ProcessInvocation process is not launched (one with this red icon on system tray).  I have tried to reinstall TD.NET twice to no avail.  I couldn't rely on Resharper's test runner since it does not detect MbUnit tests as valid TestFixtures.  WTF!

I have tried the reset switch for visual studio, still the runner is not launched, need help!

[UPDATE] I tried reinstalling IS 12 last night and TD.NET works.  I got an email from Jamie this morning that IS12 uninstall could have unregistered important COM components so we just added the following keys and TD.NET is now working without IS12.

================================================
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-000000000046}]
@="IEnumVARIANT"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-000000000046}\NumMethods]
@="7"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-000000000046}\ProxyStubClsid]
@="{00020421-0000-0000-C000-000000000046}"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{00020404-0000-0000-C000-000000000046}\ProxyStubClsid32]
@="{00020421-0000-0000-C000-000000000046}"
================================================

Filed under: , ,

Comments

# fruityoaty said on October 2, 2006 3:23 PM:

Oh man, I work as a software tester and I'm getting bad flashbacks from my last test gig which had a very poor installer setup (made with InstallShield). It f**ked up the registry. Well, it might have been InstallShield's fault... could have been the developer! Bugs, bugs, bugs.

# jokiz said on October 2, 2006 7:42 PM:

it must be the developer's since they are the one who created the installshield setup project

# cruizer said on October 2, 2006 8:47 PM:

it depends. if it was installshield's task to put stuff into the registry then it is installshield's fault. if the installshield setup project manually put in registry entries via the exposed installshield functions then it's the installer developer's fault.

# TestDriven.NET by Jamie Cansdale said on October 3, 2006 12:19 AM:

A few people have had problems with TestDriven.NET after they uninstall InstallShield. It appears that