We can easily use Set Property Custom Action to set Windows Installer Property, but sometimes we wish to set the property directly in VbScript, specially if we are taking an input from a user through VBScript. Hope this tip helps.
Many times I come across articles, where people discuss on which to choose WISE Script or VBScript while creating Custom Action in the package. Here are some advantages and disadvantages of both.
I have learned an easy way of copying condition directly in one Custom Action from other. This is totally from my own experience, and I have not found any material for it on net too. So here it goes...
Sometimes you may encounter the problem of unnecessary repairs of MSI while launching the shortcut in the same logged in user. Here is the way to troubleshoot this problem.
Is English not your first language? Maybe your users would prefer to use some other language. You can make that change and simply use the SystemLanguageID property to change the default in your system.
If there is a situation in which you have created an MSI with Merge Modules and you don't want to recompile it because of its size or re-entry of errors, but you also want to update a merge module, then this tip will help you.
