Installing MSI several times

One of the features of Windows MSI is that it can determine what version of the product is installed already and upgrade it if necessary. It uses unique product code guid to identify your product among all installed programs. This implies that product can be installed only once. But what if you have a requirement to install the same product several times on the same machine?
Microsoft suggests that you use instance transforms to do that. But this means that for each installation you need to ship a separate instance transform which is not suitable in my case.
I came up with the following script that modifies msi product code and allows you to install it as many times as you want. Each installation is identified by a unique instance name. You specify it as an Instance parameter to the powershell script below. wirunsql.vbs and wisuminf.vbs are part of Windows SDK: https://www.microsoft.com/en-us/download/details.aspx?id=3138

Comments

Post a Comment

Popular posts from this blog

TFS Proxy not working: The source control proxy is not responding

You can get this message if you are using tfs proxy. The source control proxy 'xxxxxxxxx' is not responding, so the request will be sent to the main server. Please verify your settings. Additional information: TF30063: You are not authorized to access Microsoft-IIS/7.5. ---- Summary: 0 conflicts, 1 warnings, 0 errors ---- Solution: Go to Control Panel\Credential Manager and add your tfs credentials for proxy server.
Read more

Demystifying fast up-to-date check in Visual Studio C# projects

Fast up-to-date check was created in an attempt to mitigate performance issues with incremental builds in MSBUILD. Indeed if you have many projects it would take considerable amount of time to evaluate each of them and check timestamps on all input and output files. Instead Microsoft decided to implement a simplified version of these checks that would run faster without involving MSBUILD engine. As a result this "feature" only works with "native" targets and if you have any kind of customization where external inputs or outputs are used then you'll have "misfires" sometimes. Below is some information I was able to figure out that can help you mitigate those issues. It's based on my own investigation therefore it may be not accurate enough. At least this is the most complete description that you'll find on the web. It will help you a lot in troubleshooting if you enable up-to-date check logging. Go to HKEY_CURRENT_USER\Software\Microsoft\Visua
Read more

Bitcoin, Docker, Microservices, etc.

I've been hearing a lot of buzz words lately like Bitcoin, Docker, Microservices, EventBus, etc. And you know what... every time I hear it, it drives me nuts. Not because something is wrong with those technologies but because they seem to be always abused. People are trying to use them as a silver bullet to any problem even if it doesn't exist. Or in many cases people using those buzz words have little to no idea where the problem is. They don't realize that the majority of the issues in software are due to stupid things like copy-paste, over-engineering and lack of automation. And microservices and other buzz words are not going to fix that.
Read more