You can see which component a website is associated with in the IIS view by selecting a website and look at the Component setting for the site. Then, make a note of this component name and go to the Setup Design or Components view and select the component. In the component settings, you can enter a condition for the component in the "Condition" field. More information on conditional statements can be found in the following article: Conditional Statement Syntax ... View more

That's not quite right. If you're doing a minor upgrade (change the version number without changing the product code or upgrade code), you need to set REINSTALL and REINSTALLMODE properties to upgrade, but you can't set them for a new install. (If you wrap the MSI in setup.exe, setup.exe detects the existing product and sets these properties when it launches the MSI.) If you're doing a major upgrade (change the version number and the product code but not the upgrade code), then each install is a new install and your bat file should work. On an upgrade, the MSI will detect the old version and uninstall it before installing the new version. (How it does that is based partly on the location of the RemoveExistingProducts action in the Execute Sequence; you might want to read up on that in the Windows Installer documentation to pick the scenario that's right for your product.) ... View more

Did you ever find out more on this situation? I have a user running Vista with an installer built using IS2009 and I'm seeing this error code. ... View more

in the releases view select one of your releases and you should see a series of tabs along the top of the right hand panel, one of those tabs will be "postbuild" if you select that tab and set the value for the "copy to folder" to the location you want it to drop the installers at and set the "Distribute after build" to "Yes" it will copy the installers when the build is complete. in the releases view you have a treeview Releases -+{Product Configuration} --+{Release} The {Product Configuration} and {Release} will be named differently depending on what you named them, but it is the {Release} node you want. ... View more

If nothing else, you can use the Search functionality in the Direct Editor view to find occurrences of a path variable. ... View more

Perhaps see [post=418185]this post[/post] for a technique you can use. ... View more

Those messages come from the Windows Installer engine, and offhand I don't know of a way to change them. The beginning of the log (the first line or so) should indicate the date, however. ... View more

If I map "Virtual Directory ->Content Source Path" to a different folder not in IISROOTFOLDER e.g. I map it to ProgramFilesFolder/InstallDir folder. Will this solve the problem? Is there any other way to create a vitual directory for a folder that is not in IISROOTFOLDER? Thanks. naveed ... View more

Thanks Alpesh, Detailed log with /v helped. The problem was that .ism file was already open with Visual Studio 2008. I closed the all programs that were using .ism file and then ran the IsCmdBuild.exe; it worked. Yahoo 🙂 Thanks. Naveed ... View more

SETUPEXEDIR property is set on the command line to msiexec.exe by setup.exe when the install is run through the setup.exe. This is why this property is undefined when the install is run directly from the MSI file. You may want to use the SourceDir property instead. This is a MSI property that is set by the ResolveSource action. So this means you can use the value of this property to determine the MSI location anytime after ResolveSource action. Note that by default InstallShield puts a condition on this action so that it is only run during a first-time install. SourceDir Property http://msdn.microsoft.com/en-us/library/aa371857(VS.85).aspx ... View more

After much trial and error I have finally figured out the root cause of my problem. I was using the SUPPORTDIR pre-defined constant supplied by InstallScript. This apparently changes between the UI and Execute sequences. I've changed our code to pass SUPPORTDIR through CustomActionData. Using the value passed through CAD it looks to be working now. ... View more

I have the same problem like you. If I did not mess anything; you do not have to do anything to check anything. The setup will check and will tell you (end user) what you need. If you can see my question to the forum, you would see that I was stating that an error message informed the end user's computer that .net framework (v2.0.5075)is needed to be installed. ... View more

Lurean, Thank you for your response. I am a newbie. I need to know what can be done and what cannot be done with InstallShield. Requirements are: Remotely create Db from an .mdf file, for initial install. This will be part of web application installer. Later on, for update install, run SQL Script to update schema with preserving old data. So for initial install I should use .mdf. For later updation installer I can use sql scripts. Please let me know if it will be possible. ... View more

You have to do this manually. One approach would be to set registry keys in a known location (perhaps under the application's Uninstall key, or its HKLM\Software\... key), and to read them in with system searches. ... View more

And in case anyone is interested I have found that INSTALLDIR is not actually available as a session property until After Cost Finalize. Use of Session.Property("INSTALLDIR") prior to cost finalize returns an empty string. Des ... View more