Another reason by MSI is better than NSIS
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.
This entry was posted by reggie on January 25, 2007 at 6:19 pm, and is filed under Technology. Follow any responses to this post through RSS 2.0.Responses are currently closed, but you can trackback from your own site.
-
#3 written by Goji business 3 years ago
-
#4 written by Neil 3 years ago
-
#5 written by Matt 3 years ago
-
#6 written by Randolph, NJ Licensed Electrician 3 years ago
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 … -
#7 written by Hip Hop Abs 2 years ago
-
#8 written by seo tools 2 years ago
With 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.
-
#9 written by sex toys 2 years ago
-
#10 written by Custom Research Papers 2 years ago
-
#11 written by eczema 2 years ago
-
#12 written by online games 2 years ago
-
#13 written by good credit 2 years ago
-
#14 written by Unblock Facebook 2 years ago
-
#15 written by Promotional Gifts 2 years ago
-
#17 written by link building services 2 years ago
With 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
-
#18 written by Gadget Review 2 years ago
-
#19 written by bathroom vanity 2 years ago
-
#20 written by consolidate debt how to consolidate debt 2 years ago
-
#21 written by aryz 2 years ago
-
#22 written by replica Louis Vuitton handbags 2 years ago
-
#23 written by gas rewards credit cards 2 years ago
-
#24 written by casino games 2 years ago
-
#25 written by online life insurance quotes 2 years ago
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.
-
#26 written by windows web hosting 2 years ago
-
#27 written by Facebook Proxy 2 years ago
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.
-
#29 written by Canada Immigration Guide 2009 2 years ago
-
#30 written by Betsey Johnson 2 years ago
-
#31 written by mandy 2 years ago
-
#32 written by Lucy 2 years ago
-
#34 written by willy 2 years ago
-
Comments are closed
- Comment Feed for this Post
Didn't find any related posts :(
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.