I hate MSI authoring as much as the next man and still don't know why I can't use non-GUID IDs that I select to control my components. I might have to use a GUID to identify the particular company and maybe even my particular product, but inside that product I shouldn't have to wrangle with GUIDs. But I digress...
Recently I've been looking at NSIS and wondering if it would be a better option for delivering my products. It's simpler than WiX and has a nice community following complete with a healthy library of extensions and plugins. The problem is that it's not MSI based and so there are things that MSI handles for you that you have to do manually with NSIS.
One example is making sure that Add/Remove Programs doesn't show prior versions of your app. With MSI a person simply needs to set a ProductCode and UpgradeCode (both GUIDs). With NSIS you're left with scanning for registry keys or files from the prior install and then manually updating the Uninstall registry key. Doable but just feels dirty. And it's easy to forget to do this. Here's a screenshot of my Add/Remove programs after installing Thunderbird 2.0 beta 1 and then upgrading to beta 2.
I wouldn't feel too "dirty" about scanning the registry for install/uninstall details. Not only does MSI do exactly the same thing (albeit automatically), it also copies the entire MSI into the windows directory. And is extremely awkward to patch. And gets confused when you try to apply an upgrade, unless you have a tailored setup.exe. The tricky part of writing an installer is considering the lifecycle - the uninstall, the repair, the patch rollback, the silent install. NSIS is easy to use initially because it doesn't worry about these details. MSI was build to handle them and so is inherently more complex.
ReplyDeletei think that is not the only reason
ReplyDeleteNullsoft Scriptable Install System (NSIS) is a script-driven Windows installation system with minimal overhead backed by Nullsoft, the creators of Winamp. NSIS has risen to popularity as a widely used alternative to commercial and proprietary products like InstallShield.
ReplyDeleteThe Windows Installer (previously known as Microsoft Installer) is an engine for the installation, maintenance, and removal of software on modern Microsoft Windows systems.
ReplyDeleteIs there a good explanation of the UpgradeCode/ProductCode logic? It looks like the one from the help file is too complex - because I cannot make it work the way I want :)
ReplyDeletethank you,
Use MSI if you are aiming at corportate market - no question. ... WiX is orders of magnitude easier than building MSIs yourself, but that really isn't saying much. ;-) .... found the changes from one release to another to be that disruptive. ... Are NSIS and WiX that much better? moronica. Monday, April 28, 2008 ...
ReplyDeleteHi, can anyone tell us how to improve or any other method .. i think we cannot trust MSI anymore :S
ReplyDeleteWith recent builds of the Opera beta, they released the Windows Installer version of the Opera package. Unfortunately, this has lots of problems with users running Windows 9x or NT4 preSP6. What makes matters worse is that the InstallShield version that the installer is built with uses the Windows Installer 3.x series runtime, which is the first version to not support Windows 9x or NT4 completely.
ReplyDeleteWell, i think the interface lacks something of user friendliness.
ReplyDeleteElse, i never gets annoyed with the program..i hope you will get used to it.
I hate MSI also.
ReplyDeleteVery boring at times and very slow.
Thunderbird 2 Beta 1 is a developer preview release of our next generation Thunderbird email client and is being made available for testing purposes only. Thunderbird 2 Beta 1 is intended for our testing community.
ReplyDeleteI think it is great to use it. But every one has an opinion and method of use!
ReplyDeleteNon-identifying information is data that may be obtained in most states from the agency that handled the adoption. This information must be requested in writing by most agencies.
ReplyDeleteyou are un-identifying person but you write here a good nasty blog with your great thought,thanks for sharing man#
ReplyDeleteYes MSI is better than NSIS i think. I get frustrated also with MSI
ReplyDeleteIndeed much better friend. I recommend you NSIS. Betterness
ReplyDeleteWith recent builds of the Opera beta, they released the Windows Installer version of the Opera package. Unfortunately, this has lots of problems with users running Windows 9x or NT4 preSP6. What makes matters worse is that the InstallShield version that the installer is built with uses the Windows Installer 3.x series runtime, which is the first version to not support Windows 9x or NT4 completely
ReplyDeletethis can be very slow at time , the author is right about its frustating nature sometimes it gets to your nerves.
ReplyDeleteThe tricky part of writing an installer is considering the lifecycle - the uninstall, the repair, the patch rollback, the silent install. NSIS is easy to use initially because it doesn't worry about these details. MSI was build to handle them and so is inherently more complex.
ReplyDeleteThe tricky part of writing an installer is considering the lifecycle - the uninstall, the repair, the patch rollback, the silent install. NSIS is easy to use initially because it doesn't worry about these details. MSI was build to handle them and so is inherently more complex.
ReplyDeleteI think we should wait till they make a better version of the MSI before using this software with others. I find it hard to use it with other software, so instead of having it easier, I'd mix it up and make it a lot worse.
ReplyDeletehttp://onlinecasinospotlight.com
egistry keys or files from the prior install and then manually updating the Uninstall registry key. Doable but just feels dirty. And it's easy to forget to do this. Here's a scre
ReplyDeleteThe tricky part of writing an installer is considering the lifecycle - the uninstall, the repair, the patch rollback, the silent install. NSIS is easy to use initially because it doesn't worry about these details. MSI was build to handle them and so is inherently more complex.
ReplyDeleteIt's simpler than WiX and has a nice community following complete with a healthy library of extensions and plugins. The problem is that it's not MSI based and so there are things that MSI handles for you that you have to do manually with NSIS.
ReplyDeleteProductCode and UpgradeCode (both GUIDs). With NSIS you're left with scanning for registry keys or files from the prior install and then manually updating the Uninstall registry key. Doable but just feels dirty. And it's easy to forget to do this. Here's a screenshot of my Add/Remove programs after installing Thunderbird 2.0 beta 1 and then upgrading to beta 2.
ReplyDeleteI completely agree with you on the sisplay of prior programs. Nice Post , i am cinvinced that MSI is better than NSIS.
ReplyDeleteRecently I've been looking at NSIS and wondering if it would be a better option for delivering my products. It's simpler than WiX and has a nice community following complete with a healthy library of extensions and plugins. The problem is that it's not MSI based and so there are things that MSI handles for you that you have to do manually with NSIS.
ReplyDeleteI think NSIS is much better. MSI is way to slow for me.
ReplyDeleteIt's simpler than WiX and has a nice community following complete with a healthy library of extensions and plugins. The problem is that it's not MSI based and so there are things that MSI handles for you that you have to do manually with NSIS.
ReplyDeleteHmm strange this post is totaly irrelevant to the search query I entered in google but it was listed on the first page.
ReplyDeleteIt's simpler than WiX and has a nice community following complete with a healthy library of extensions and plugins. The problem is that it's not MSI based and so there are things that MSI handles for you that you have to do manually with NSIS.
ReplyDeleteThe tricky part of writing an installer is considering the lifecycle - the uninstall, the repair, the patch rollback, the silent install.
ReplyDeleteGreat post - keep it up man :)
ReplyDeleteIt's simpler than WiX and has a nice community following complete with a healthy library of extensions and plugins. The problem is that it's not MSI based and so there are things that MSI handles for you that you have to do manually with NSIS.
ReplyDeleteSources...
ReplyDelete[...]here are some links to sites that we link to because we think they are worth visiting[...]...