InstallAware

I have a web based install. In order for a repair scenario to work correctly would each version of the product need its own updated version folder for the client install to find?

Do implementers out there keep all published versions of the product in different folders on the website?

If there is only the latest version on the website would the repair possibly get a newer version and result in a "hosed" installation? Would the IA runtime check the version GUID and error out if it does not match the current version being repaired.

What happens in the case of adding options? If there is only a single version (latest one) available, it is possible that the runtime could fetch a newer version of a component and again result in a "hosed" installation?

Good question, which first of all I presume pertains to re-use of web media blocks, right?

If so, it shouldn't be a problem. You might run into a strange new novel issue, of course, but web media blocks are designed so that they can be shared across multiple projects. The setup engine adjusts the layout such that they are re-usable not only across versions, but also different products (as in the case of application runtimes, for instance).

I can only foresee a "hosing scenario" when you are generating MSI file hashes and files inside your web media blocks change between versions, causing the hashes to fail.