Check out this thread: http://community.installshield.com/showthread.php?t=169856&highlight=multiple+instance I've implemented multiple instances, but didn't use the ISProductConfigurationInstance table because I needed more advanced functionality. My solution runs a vbscript to generate the transform and embed it into the MSI. If you're interested I can give you some details about it. One difference vs Christophers approach is that my MSI cannot be embedded into setup.exe. ... View more

Try using MsiSetTargetPath. Before a certain action, ResolveSource I think, you can modify INSTALLDIR using MsiSetProperty - afterwards you have to use MsiSetTargetPath. Logging an upgrade is the same as a new install. Use /lvoicewarmupx with msiexec.exe or /v"/lvoicewarmupx " with setup.exe. ... View more

Take a look at the InstallWelcome dialog in the Dialogs view. You'll see several places where the [ProductName] property is used. At runtime this gets replaced with the ProductName from the Property table. You can do this for any property including the [ProductVersion] property. Does that answer your question? ... View more

Each virtual dir is associated with a component. You can put a condition on the component to determine whether the virtual dir is created or not. Look on the General tab of the Virtual Directory properties to see what component its associated with. ... View more

I'm not familiar with this problem but I'll throw out an option. You could use a VM or a physical machine that's not on the domain - logging on w/ an admin account. ... View more

Select Media -> Upgrades, then right-click on "Upgrade Windows Installer Setup" to add new upgrades. ... View more

I don't fully understand your question, but you can use the version number in a SQL script by doing a text replacement. See the Text Replacement tab when your script is selected in the IDE. It's best to have some known token for the "Find What" and use the property in brackets for the "Replace With" value. e.g. [ProductVersion] ... View more

Chris, You'll need to write a custom action to read the XML values. Then you can save the values in properties and use those properties to write the values back using the Xml File Changes view. ... View more

Are you talking about an installer DLL or writing custom actions in .NET? With an installer DLL you need to inherit from the System.Configuration.Installer class and configure the component to use the class. If you're writing custom actions in .NET you need to write your DLL in C++/CLI (.NET 2.0) or MC++ (.NET 1.1) so that you can export functions. Note that Microsoft states that .NET custom action DLL's are not supported but there are several people on this forum that have done it successfully. ... View more

What do you mean by "shared"? Is there only supposed to be one copy of the DLL on the machine that both applications load? Or do both applications have their own copy of the DLL? If you only want one copy of the DLL on the machine then go with the merge module approach - it's a project type so just create a new merge module project for the shared DLLs. If both applications have their own copy of the DLL then you don't have to do anything special - just include them in both installs. If you have a choice I'd let each application have it's own copy of the DLL. That can prevent support issues caused by version incompatibilities. e.g. User installs Application A with version 1.0 of a shared DLL. User then installs Application B with version 3.0 of a shared DLL. Now Application A is using version 3.0 of the shared DLL also so if a function is not backward compatible then Application A is broken. JMHO ... View more

Also with IIS 7 the application pools are being set to use .NET 2.0 even though they are v1.1. If you'd like a project to duplicate these issues let me know. ... View more

David, I think I've got another one for you. When installing on IIS 7 you can't use a property for the application name. The log doesn't provide any details. If you need any additional information let me know. Thanks ... View more

Thanks David. ... View more

Okay, here's an example. There are two custom actions that call a batch file. The first one uses the run an executable custom action type which will work if you don't need to do any complex processing before running the batch file. The second one uses InstallScript to launch the batch file. Hope this helps. ... View more

Logging/debugging won't help. The issue is that there are only 3 properties that can be accessed by a CA running in deferred mode: CustomActionData, ProductCode, and UserSID. The CustomActionData is a way to pass data from a CA running in immediate mode to a CA running in deferred mode. Based on your example that might not be necessary though. If I have time tomorrow I'll setup an example project for you. ... View more