asked on

InstallShield: Why is my web service extension not recreated on upgrade?

I have a basic InstallShield MSI installer that sets up a web service extension for ASP.NET 2.0. I am now updating the MSI to include a major upgrade. The upgrade includes the same WebServiceExtensionComponent with the same GUID. However, after running the upgrade, the extension is gone in IIS. The Upgrade removes it as expected (Because I checked the "overwrite" box), but does not recreate it. Ideas?
WebServiceProblem.JPG

pureauto

ASKER

Update: This only happens if the Major Upgrade Settings option is set to "Install setup then remove unneeded files.

Vadim Rapp

please produce detailed installation log and post. And tell the component name.

pureauto

ASKER

The component name is WebServiceExtensionComponent. All I am really trying to accomplish with this component is to enable ASP.NET 2.0 Web Service Extensions. I don't want to remove the extension on uninstall which it appears to be doing.
log.txt

ASKER CERTIFIED SOLUTION

Vadim Rapp

membership

Create a free account to see this answer

Signing up is free and takes 30 seconds. No credit card required.

See answer

pureauto

ASKER

Both install to the [InstallDir]. However, the name of that directory has change between the original version and this one. When I change the name back to the original, it fixes the web service issue, but creates another issue: the old virtual directory is not removed (The name of the virtual directory has also changed). Also, the contents of the install directory are not overwritten. Can this problem be solved without reverting the name of the install dir?

Vadim Rapp

What gets overwritten is controlled by version numbers, mainly. It's all really hard to tell without seeing the actual installation. See, this forum, EE, is mostly for well defined, contained technical questions: this is given; this is the problem. "old virtual directory is not removed", I'm sure you understand, can have many reasons, many things to look at (how is it specified in the installation, to begin with), and it's very hard to tell "blindly". Would definitely again involve looking in the installation log, as the beginning. See my email reply that I sent.

pureauto

ASKER

I think I will end up having to create two upgrade packages. One to be run immediately after the other. It is less than ideal, but will have to suffice in my situation.

pureauto

ASKER

Thanks again.