English 中文(简体)
NSIS Vs WiX Vs AnyOther Installation Package
原标题:

Need to create a Installation Package that would need to a) install a Database, b) create database and tables, c) installed already created installable in Visual Studio, d) create ODBC datasource, e) copy files. f) create shortcuts, etc

Can you please suggestion which one to use? To simplify following would be my criteria(Descending Order)

  1. Stable
  2. Fullfill all my needs.
  3. Easy to learn

Can you please suggest?

最佳回答

If you want to use WiX, you need at least a basic understanding of how Windows Installer works. The best reference around is The Definitive Guide to Windows Installer, which runs through the all basics with examples using Visual Studio and Orca.

WiX is very easy to learn once you understand Windows Installer.

A properly written Windows Installer package will be more stable and resilient than anything else you can imagine. It ll take a month or so to get your head around it, and you ll get better and learn more about it over time.

On the other hand, NSIS only takes a day to learn - it s just a simple scripting language.

@wcoenen - I d agree that you definitely will learn more by reading various blogs of those on the WiX team, but I personally find that particular book gives a really solid foundation which makes it easier to understand the concepts they re talking about.

@Sandeep - You need an MSI package for corporate software, if you have no intention of selling your product to customers who need automated deployment in a locked down environment then NSIS will suit you just fine :)

@romkyns InnoSetup is fairly limited in my opinion, you can do just as much with a batch file and a self extracting EXE - it all comes down to your target market, corporate/enterprise clients demand MSI - home users don t care as long as it works and would happily double click on a SETUP.BAT file :)

问题回答

I would like to suggest another installer which is InnoSetup combined with ISTools

Innosetup has very good scripting language, and has a wizard to make it easy for you do the installation package and ISTools have the GUI interface for most of Innosetup options,

I was able to Install Mysql, its service and creating tables and other things with it, and it s much easier to learn than others.

It depends on what you are trying to install. If it is a simple application installation, then NSIS is fast and easy to implement (wix has a very bad documentation). But if your installer does some changes in Windows OS, like, creating restore point, installing kmdf or umdf driver, then WIX is much better than NSIS.





相关问题
Correct place to install demostration projects?

With the new Windows 7 restrictions (well, new to Windows Vista anyways), we can no longer install demo projects to %ProgramFilesFolder%OurApplicationdemo since restricted users will not be able to ...

.deb package conffiles problem

I am distributing one of my applications using a .deb package, but have a problem relating to one of the files. The distribution includes a database file which is constantly updated by the app, on a ...

Closing an application using WiX

In creating my WiX installer I have run into an issue when trying to close an application before installing the upgrade. Below is an example of how I am attempting to do this. <util:...

VS 2005 Setup - HKCU

I am trying to fix an existing application that uses a Visual Studio 2005 setup project. We are requiring it to work on limited user accounts for XP, our app is written in C# for .Net 2.0. It writes ...

Do I want Publish or Release Build in VB.net?

I wrote a little (like 40 lines little) Winforms application with VB.net in Visual Studio 2010. Now I ve released the code as a Google Code project. It s easy for a developer to get the source but I d ...

configsource and installer

I have an project csproj, with app.config file, and logging Ent.Library section using configsource attribute. The logging section is in ahother file Configloggingconfiguration.config. I have a ...

热门标签