Handling File Extensions during Uninstall
Hi All,
Just hoping to get some feedback on how you approach the problem of the MSI ripping out file extensions.
Say you install an app that overwrites extensions already on the build. When you uninstall it removes those extensions completely.
I'm trying to put together a standard approach to handle this problem.
At the moment there are some mixed opinions on this.... some say leave the MSI to behave as per the source binaries..... others to restore the builds extensions using a VBScript at uninstall.
Cheers.
Just hoping to get some feedback on how you approach the problem of the MSI ripping out file extensions.
Say you install an app that overwrites extensions already on the build. When you uninstall it removes those extensions completely.
I'm trying to put together a standard approach to handle this problem.
At the moment there are some mixed opinions on this.... some say leave the MSI to behave as per the source binaries..... others to restore the builds extensions using a VBScript at uninstall.
Cheers.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
nheim
17 years ago
Hi islander222,
the best thing, i can imagine, that an app, which is manipulating the extensions, should backup the existing state to a secure and own location, like the uninstall reg key. From there, on unistall, it can be restored with a script or program.
This is one of the weak spots of MSI, where you are completely on your own.
Regards, Nick
the best thing, i can imagine, that an app, which is manipulating the extensions, should backup the existing state to a secure and own location, like the uninstall reg key. From there, on unistall, it can be restored with a script or program.
This is one of the weak spots of MSI, where you are completely on your own.
Regards, Nick
Posted by:
islander222
17 years ago
Thanks Nick,
Thats someting I was considering, but could be alot of extra work (depending on the number of effected extensions).
Another option could be to install the extensions via the registry adding them to the HKCU hive - that way when they are removed the extension in the HKCR\HKLM hive will kick in.
I was hoping there would be more discussion on this topic - as I know alot of packages have this issue. And I was interested to know how others tackle this problem?
Regards,
Aidy.
Thats someting I was considering, but could be alot of extra work (depending on the number of effected extensions).
Another option could be to install the extensions via the registry adding them to the HKCU hive - that way when they are removed the extension in the HKCR\HKLM hive will kick in.
I was hoping there would be more discussion on this topic - as I know alot of packages have this issue. And I was interested to know how others tackle this problem?
Regards,
Aidy.
Posted by:
rpfenninger
17 years ago
Hi Aidy
I consider this a very interesting thread. I recently had 'that issue' as well with the new WinZip package. As the .zip extension is already in the Windows XP Build.
However, when I tested the uninstallation I noticed, that Windows is again able to open .zip files through the original extension. The only thing is, the icon is wrong.
Since I think, the only moment when WinZip gets uninstalled in our shop is at the time, when a newer version (which rearranges the .zip extension anyway) gets installed I did not consider this as a problem.
However you motivated me, to spend more time on this on the next package.
Cheers
Roland
I consider this a very interesting thread. I recently had 'that issue' as well with the new WinZip package. As the .zip extension is already in the Windows XP Build.
However, when I tested the uninstallation I noticed, that Windows is again able to open .zip files through the original extension. The only thing is, the icon is wrong.
Since I think, the only moment when WinZip gets uninstalled in our shop is at the time, when a newer version (which rearranges the .zip extension anyway) gets installed I did not consider this as a problem.
However you motivated me, to spend more time on this on the next package.
Cheers
Roland
Posted by:
AngelD
17 years ago
FYI
The WinZip & Compressed Folder issue is handled by register or unregister the "SystemFolder\zipfldr.dll" file depending on the Compressed Folder support. The WinZip installation will unregister the zipfldr.dll during installation.
The WinZip & Compressed Folder issue is handled by register or unregister the "SystemFolder\zipfldr.dll" file depending on the Compressed Folder support. The WinZip installation will unregister the zipfldr.dll during installation.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.