Good question, I'd like to know the answer too as it looks like the parameter we need has been removed but not from the documentation. ... View more

It appears that I can workaround this issue by overriding the following InstallScript functions like so so that they only do what they do if the feature that has IIS in it has been selected... function int OnIISInitialize() string szSettingsFile; string szRuntimeFile; begin if (FeatureIsItemSelected(MEDIA, "My Web Feature") = TRUE) then // Initialize IIS runtime szSettingsFile = SUPPORTDIR ^ IISRT_INI; szRuntimeFile = SUPPORTDIR ^ IISRT_DLL; return IISRTInitialize( szSettingsFile, szRuntimeFile ); else return ISERR_SUCCESS; endif; end; function int OnIISComponentInstalled(szComponent) begin if (FeatureIsItemSelected(MEDIA, "My Web Feature") ) = TRUE) then return IISRTComponentInstall( szComponent ); else return ISERR_SUCCESS; endif; end; It's also odd that we don't get this with another product installation that has a similar selectable IIS feature. The installation that has the problem has NT Service object components. We know there have been previous InstallShield bugs regarding using NT Service objects and IIS in the same installation so perhaps there are some more bugs still in there. ... View more

We just upgraded to 2012 to get a different bug fix and unfortunately this problem with prerequisite dialogs not working with your own skins is still there. :mad: ... View more

InstallShield 2012 does indeed include the bug fix listed in the 2011 release notes. Is there some way we can get IOB-000058755 fixed in InstallShield 2010 as a patch as we really don't want to have to upgrade to 2012 just for one bug fix as we don't need any of the other new features or changes? ... View more

Many thanks. ... View more

I would like to know the answer to this too as this is one of the reasons we're still using InstallScript projects and not MSI because we can control this kind of thing from script in InstallScript. ... View more

SherylSikora wrote: The URL for the download that will give you the objects that you are looking for can be found here: https://installshield.subscribenet.com/control/inst/AnonymousDownload?dkey=5423951 Thanks! Do you also have a link for "InstallScript .NET Objects" too? I'm also trying to evaluate 2012 as an upgrade for our 2010 version as the release notes for 2011 details a fix for a bug we have got in our version but I need the .NET Framework objects as they are part of our existing InstallScript installation. ... View more

Shark75 wrote: or we make all prerequisites hidden so the dialog doesn't come up at all or we don't skin. In fact we can't even do this cause if a prerequisite is needed the dialog that displays whilst it installs has the same problem of the standard bitmap sitting on top of our corporate skin. Is it possible to get a fix for this because we can't use a skin with it like this? ... View more

I have a similar problem in IS 2010 Premier. Our installations are skinned, so when the pre-requisities dialog comes up the standard bitmap that displays on the left hand panel sits on top of our skin instead of being hidden. There seems to be no way to stop the bitmap coming up because the earliest you can code the following in (which turns off the bitmap on the left panel): DialogSetInfo(DLG_INFO_ALTIMAGE, "", TRUE); is in OnBegin() which is after the prerequisities dialog appears. This is just really ugly so we either don't use prerequisites at all or we make all prerequisites hidden so the dialog doesn't come up at all or we don't skin. None of which are great solutions as we would like users to see what they are being told to install before it happens and we have to use skins to keep a consistent corporate image. ... View more

Thanks. I see you are doing the text substitution very early on in OnBegin. How late in the installation sequence can text substitutions be made? I must admit that setting the application to 64-bit and the application pool to don't allow 32-bit to run in the project settings works on all platforms that I've tested it on, 32 or 64-bit, 2003, 2008, 7 or Vista. The 32-bit OSs just ignore the 64-bit setting. ... View more

I have the same issue on Vista 64 (to be precise it's Windows 2008 64-bit). I try to use RegDBGetKeyValueEx and on all OSs it reads the entry correctly, but not on this OS. My project is InstallScript (not MSI) and I have tried turning UAC off and running the setup.exe as Administrator, but still have the same results. In the particular example I'm detecting whether the user has the IIS 6 Metabase compatibility option installed or not. RegDBSetDefaultRoot(HKEY_LOCAL_MACHINE); // Check whether the Metabase registry key exists. if (RegDBGetKeyValueEx("SOFTWARE\\Microsoft\\InetStp\\Components", "Metabase", nvType, svValue, nvSize) < 0) then // Display error to the user. MessageBox("Error: Setup has detected that the IIS 6 Metabase Compatibility component is not installed.\n\nSetup is unable to continue.", SEVERE); // Fail the requirement. bvResult = FALSE; endif; Did you find out why this was not working for you? ... View more

It seems that the installation where the ASP version was set but not the platform has corrupted the IIS metabase. Using IIS Metabase Explorer I can see the virtual directory there, but configured right and it does not appear in IIS Management Console. Using IIS Metabase Explorer I've cleaned up the badly installed virtual directory and now, when the platform is set to 64-Bit and the application pool is set to don't allow 32-bit apps to run, it installs ok. It does highlight that InstallShield is corrupting the IIS metabase when the platform is not set and installing on Windows 2003 Server 64-bit. ... View more

I must admit I can't get your instructions to work on an MSI project either and nor can I build any sort of project that successfully installs a Web Application on Windows 2003 R2 64-Bit (IIS 6), even if I specifically set everything to 64-Bit. I'm currently resorting to trying to create a virtual directory for this particular OS by hand in the script. Are you able to create a Web Application on Windows 2003 R2 64-Bit using InstallShield's IIS functionality? ... View more

Thanks for the reply. I understand whay your saying, although it would be nice if InstallShield did this for you if it knows IIS 6 plays silly kippers with this. I've tried implementing your suggested solution, but I can't get it to work in InstallScript. I'm not sure I understand fully what you are supposed to do in InstallScript projects. Currently I've added the property using the Direct Editor as suggested with instead of [ASP_NET_VERSION] in the MetaDataValue. If you actually look at the ism file it adds this as a reference to a new string in the string table that has the text . Then in the Feature Installing function of the Web Server feature I call TextSubSetValue(" ", "x64", TRUE) (if it's 64-bit) or "x86" if it's 32-bit (determined using SYSINFO.bIsWow64). This didn't do anything so I added TextSubGetValue to the same method and displayed it in a MessageBox and the value is blank, so it's obviously not substituting the text. I've tried editing the ism file by hand so that (or <ASP_NET_VERSION> to be precise) is in the property value rather than a reference to a string table value, but still no joy. There is no ISIISCosting function in the help or in the drop-downs to add either, so I couldn't look at sticking it there instead of in the Feature Installing function for the feature. Could you elaborate more on how to implement this in InstallScript projects? Thanks. ... View more