1 reply to this topic

[Matthias1967]

Hello,

When installing Multiple Instances of a Product, why don't I have to set new component codes for each component of the second etc. instance? As far as I have understood component codes (I may be wrong), Windows Installer does not install a component again if it is already there.

My actual issue is a "branded" install: Several "brand" developers can add their files (via merge modules) to one setup framework which contains logic, registry entries, etc. but no files ot be installed. Each brand then gets its Product Name, Product Code, Upgrade Code, Package Code. The end-user shall be able to install multiple brands besides each other (target directories are predefined subdirectories of one common directory).

So far, the component codes within the framework are the same for all brands. How do components from the framework interfere with each other?

Best regards,

Matthias

[wicampbell]

Here is an interesting and informative thread that you may find helpful:

http://groups.google...5dbd78c3c0a7e6e

Components are tracked by both product code and component id as evident by the MsiGetComponentPath function.

http://msdn.microsof...112(VS.85).aspx

We had the same concerns with our application framework, so I did a little leg work to understand the implications.