views:

3450

answers:

8

I'm need to choose a software package for installing software. NSIS and WiX seem promising. Which one would you recommend over the other and why?

Feel free to offer something else if you think it's better than these two.

+3  A: 

NSIS will give you an exe, WiX will give you a MSI.

I have used NSIS to package up a couple MSI installers into a single exe and do some additional checking I couldn't figure out how to do using the VS.NET Setup project.

INNO Setup is another installer you may want to look at. It is closer to NSIS then WiX but the installers it makes look more like standard installers then NSIS installers do.

I did not use WiX because I did not like the XML definition language used to build the installer and I couldn't figure out if it supported packaging up other dependent MSIs

Of the three I liked NSIS best as it had the best documentation.

Darryl Braaten
+14  A: 

If you want to get an installer done today, with the minimum amount of overhead, use NSIS. Simple scripting language, good documentation, fast.

If you want to build MSI files, integrate with the Windows Installer transactional system, and have plenty of time to devote to learning the declarative model used by Windows Installer, then check out WiX.

Shog9
not quite written neutraly (therefore -1), but comes to the point. It does not matter, if you need to learn either of the two, both will cost you time. Either has its good points, NSIS is independent, with wix you get the windows installer integration.
BeowulfOF
If you want to get it done **before lunch** grab InnoSetup + IStool instead - that way you don't need to use an assembly-like programming language that NSIS uses.
romkyns
Steve Wortham
+1  A: 

Personally I've only tried WiX. It has a slightly steep learning curve (unless you manage to find a nice graphical UI for it), but should pay off in the end because it uses the Windows Installer format (MSI) rather than a custom EXE as (I believe) NSIS does. The declarative approach of WiX/MSI is generally favoured nowadays, and is considered more reliable. However, if you just want a quick and easy solution, NSIS might be the option as it ought to have many samples and a good support base (though personally I would just use a Visual Studio setup package for something like that). This blog post seems to discuss the matter pretty well.

Noldorin
+1 for the link to a good discussion
Tim
+1  A: 

I use NSIS at work (I brought it in and converted our old InstalShield stuff), and I do like it.

I can't speak for the other options, but NSIS can be tricky for more complicated installer flow and the scripting language is kind of raw for more detailed kinds of things (more like assembler than a high level language).

crashmstr
+9  A: 

Also, maybe give InnoSetup a shot. Sure, you might find it to be a bit strange as it forces you to write custom code in Pascal, but then again, there's hardly anything any more that forces you to actually do custom code - IS is really, really powerful.

IS also generates .EXE installers - if you want your application to be easily deployable in enterprise environments, you'll probably have to go the WiX route, though personally, I've had quite the share of MSI related problems as a user that I personally would prefer MSI die a slow and horrible death (well - actually, a quick death would be favorable at this point - but horrible it can very well be), so just go ahead and do the exe thing.

So.

  • NSIS: Requires you to learn a new (albeit C-like) language. Creates EXE-installers.
  • WiX: Declarative Setup Creation, although a bit low-level. It certainly requires some fundamental MSI knowledge which I find really hard to optain through the general lack of easy tutorials.
  • InnoSetup: Allows you to create quite powerful .EXE installers with an easy, largely .INI-File based syntax, but forces you to learn Pascal if you need custom coding.

As a long-time delphi coder, I'd always go InnoSetup, though that's probably very biased (I'm a InnoSetup fan since around 1996)

pilif
NSIS uses a stack based batch language, nothing at all like C
Darryl Braaten
InnoSetup is great.
John Nolan
I'm curious, what were the MSI related problems?
Wim Coenen
+4  A: 

This is pretty much a duplicate of http://stackoverflow.com/questions/3767/what-is-the-best-choice-for-building-windows-installers so I suggest you check out the many, many answers over there (there's some discussion of the commercial alternatives there too)

The question you need to ask yourself is do I need to be compatible with corporate deployment scenarios for SMS/Active Directory deployment? If the answer is yes, then learn the MSI fundementals.

If you want to ship an app that's really just for fun or doesn't need to be supported on a corporate environment and you're not wanting to spend lots of time getting up to speed then learn NSIS.

sascha
A: 

You should take a look at InstallJammer. Not only is it free, it's cross-platform and very easy to use. Most common actions don't require any scripting at all, but with a powerful scripting language underneath the hood, you can make an install do just about anything you want.

If all you want is a basic installer to install your application, you can have it built in a matter of minutes from the first time you start it up. If you want something more powerful, the capabilities and documentation are excellent.

A: 

+1 for Inno. Not a fan of NSIS

Tim