june1212
7th October 2009 20:36 UTC

How to generate MSI file from NSIS
I have an installer.exe generated from NSIS. But I want a msi file. By just changing the file extension, msiexec doesn't recognize the package, saying it is not a valid package.

I tried to use msiexec to avoid the UAC prompt on Vista.

Anders
7th October 2009 20:49 UTC

NSIS does not generate MSI files, try wix.sourceforge.net if you want MSI

madden
29th December 2009 11:26 UTC

I think the supported installer output format (.exe/.msi) should be clearly stated in the product documentation. Or at least in the FAQ.

I just had to read the product help's table of contents, the product features list, the FAQ and the forums just to find I should not expect .msi output from NSIS.

A search or index lookup in the product's .chm file simply shows nothing on "msi". A simple note saying at least "only .exe is supported" would be nice.

The main features of .msi are the automated rollback it provides in case of errors or user canceling or when uninstalling, and the .msm format for merge modules which is rather standard for installing third-party libraries now. In NSIS you have to actually check for errors and script any rollback explicitly, and .msm files can be installed with NSIS with some tricks, but it should have built-in support for them. And for .msi output if possible ...

Thank you,
Timothy Madden

{_trueparuex^}
29th December 2009 12:10 UTC

NSIS creates stand-alone installer executables.

MSI (Microsoft Installer Package) is not an installer. MSI files are packages that contains installation information for the Windows Installer engine.

PaR

madden
29th December 2009 12:35 UTC

Of course.

But I would still like to see this information in the product's documentation instead of searching forums on the internet for it ...

MSG
29th December 2009 14:41 UTC

NSIS and MSI (and Inno) are entirely different things. It doesn't make any sense to name all the things that some application is NOT. Would you expect Microsoft to add a disclaimer in the Microsoft Windows Vista manual stating that "this software is not a Macintosh operating system"? Or a bottle of milk stating "Note: this bottle does not contain Coca Cola"?

Wizou
29th December 2009 16:58 UTC

Well.. Personnally I agree that this information could be added to the documentation. MSI packages are becoming quite common in the world of Windows..
So we can expect this type of question from people looking for an installer system and comparing them..

madden
30th December 2009 18:00 UTC

At least a note under OutFile or in the features list saying

Currently the NSIS compiler can only create an installer as an executable program.