This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
MorneJoubert
Level 3
‎Jun 29, 2010 07:20 AM

.NET files with key not uninstalling

I am using Installshield 2010 with an Installshield MSI installer.

Any .NET file (exe or dll) that has a key set doesn't get removed when uninstalling.

If I remove the key from the file then it is removed.
I tried seeing if the shared option would do the trick but no luck.

All the other non .NET exe,XML & config files get removed when uninstalling.

What is the magic settings to get .NET files to uninstall ?

:confused:
Labels (1)
Labels
0 Kudos
(6) Replies
Bineesh
Level 6
‎Jun 29, 2010 08:26 AM

Check if you set "yes" to the permenent property of the component.
0 Kudos
MorneJoubert
Level 3
‎Jun 29, 2010 08:34 AM

The following screenshots show all my settings

Preview file
12 KB
0 Kudos
Reureu
Level 10
‎Jun 30, 2010 01:40 AM

Here are a few questions which might help to troubleshoot this issue:

  • You mentioned:
    Installshield MSI installer
    Did you mean Basic MSI Project? Or InstallScript MSI Project?
  • Does the problem occur on all target PC's?
  • Have you made sure that the .NET assemblies were not already present in the target folder before installing?
  • Are you installing these .NET assemblies to the GAC?
  • Which OS are you running? Does this occur on all OS's? Or only on Windows Vista/Windows 7?
  • Have you tried to log the deinstallation to see what's going on?
    msiexec /x "YourMSIPackage.msi" /L*vx C:\LogfileUninstall.log

0 Kudos
MorneJoubert
Level 3
‎Jun 30, 2010 02:50 AM

I am using the InstallScript MSI Project.

I tested it (the single setup.exe) on another machine and it works fine...

That means there must be some reference counts on the filenames or components somewhere in the registry on my development machine?
0 Kudos
Reureu
Level 10
‎Jun 30, 2010 02:56 AM

Do a registry search on the affected PC, looking for the name of your assemblies. It probably still has some left-over references to them after you have deinstalled your application.

I have seen such situations in the past.
Someone had manually overwritten assemblies in the installation folder, with higher DLL versions than the ones in my setup.
They were not overwritten at installation, and were not removed either at deinstallation.
0 Kudos
MorneJoubert
Level 3
‎Jun 30, 2010 03:28 AM

Deleting all the assembly references in a few places in the registry solved the problem.
Thanks
0 Kudos