Using MSI to distribute updates
Using MSI as the deployment method for your updates fits all categories of updates, since it reuses existing processes. If you deploy new applications and packages with the help of MSI, why not use the same process for deploying updates? I fully understand that kind of reasoning. Using MSI might not be the most effective method when taking bandwidth and speed into consideration, but using processes already in place are often more important. Using MSI to deploy a new version of your package will require the whole package to be downloaded by your clients. The MSI that ThinApp generates is capable of replacing existing deployments. The parameters in use for a successful replacement of existing packages are MSIProductVersion, MSIProductCode, and MSIUpgradeCode found in the MSI section of Package.ini. If you create your new version of the package by modifying the old project folder, you should only have to activate and change the MSIProductVersion value, providing...