This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Uninstall Removes Virtual Directory
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 06, 2009
04:13 PM
Uninstall Removes Virtual Directory
We've just discovered an issue with our virtual directories that I'm hoping someone may have a work around for it.
We are using an InstallScript project that creates virtual directories. The project originated in IS12, upgraded to IS2008, then IS2009, and will probably go to IS2010.
The version of our software has also been upgraded, with our releases coinciding with our usage of version of IS. Meaning, version 1.0 of our product was done in IS12, version 2.0 is in 2009 (no 2008 due to timing), version 3.0 is also in 2009, may be 2010.
So, in version 1.0, we create a virtual directory, VDIR pointing to C:\Program Files\Version1.0. In version 2.0, the user installs to C:\Program Files\Version2.0, but uses the same virtual directory VDIR. We have a function that updates the path in IIS, so now VDIR is correctly pointing to the 2.0 location.
If we uninstall 1.0 (the IS12 installer), the 2.0 product and the upgraded VDIR remains on the system, no problem. We tested this before release, and we were happy.
Thinking that the same would be true from upgrading 2.0 to 3.0, now installing to C:\Program Files\Version3.0, and updating the path in IIS so VDIR points to the correct 3.0 location, if we now uninstall 2.0, the virtual directory VDIR also gets removed, even though the path has been modified, and it was installed by the new installer. This is behaving differently than the IS12 uninstall. This is a problem.
So, any thoughts on what we can do to the version 3.0 installer to tell the version 2.0 uninstaller to NOT remove the virtual directory if the 3.0 installer is upgrading an existing one?
We are using an InstallScript project that creates virtual directories. The project originated in IS12, upgraded to IS2008, then IS2009, and will probably go to IS2010.
The version of our software has also been upgraded, with our releases coinciding with our usage of version of IS. Meaning, version 1.0 of our product was done in IS12, version 2.0 is in 2009 (no 2008 due to timing), version 3.0 is also in 2009, may be 2010.
So, in version 1.0, we create a virtual directory, VDIR pointing to C:\Program Files\Version1.0. In version 2.0, the user installs to C:\Program Files\Version2.0, but uses the same virtual directory VDIR. We have a function that updates the path in IIS, so now VDIR is correctly pointing to the 2.0 location.
If we uninstall 1.0 (the IS12 installer), the 2.0 product and the upgraded VDIR remains on the system, no problem. We tested this before release, and we were happy.
Thinking that the same would be true from upgrading 2.0 to 3.0, now installing to C:\Program Files\Version3.0, and updating the path in IIS so VDIR points to the correct 3.0 location, if we now uninstall 2.0, the virtual directory VDIR also gets removed, even though the path has been modified, and it was installed by the new installer. This is behaving differently than the IS12 uninstall. This is a problem.
So, any thoughts on what we can do to the version 3.0 installer to tell the version 2.0 uninstaller to NOT remove the virtual directory if the 3.0 installer is upgrading an existing one?
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Nov 28, 2009
08:48 AM
find the action for removing virtual directory I dont remmeber the name but go the the names of the custom action and you would recognize it with the name and dor that action give the condition
for uninstallaitaiton NOT INSTALLED
for uninstallaitaiton NOT INSTALLED
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Dec 10, 2009
01:43 PM
We're using InstallScript, I don't think we can do that.
It's just a little frustrating that this worked in installations between IS12 and IS2008, but IS2008 breaks IS2009.
It's just a little frustrating that this worked in installations between IS12 and IS2008, but IS2008 breaks IS2009.
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)