Related Posts

8 Comments Already

commenter
Andrew Said,
February 10th, 2009 @3:51 pm  

NSIS doesn’t make .MSI files. NSIS makes .EXE installers, which are different and can’t be installed using Windows Installer like .MSIs.

commenter
Joey Said,
September 11th, 2009 @7:47 am  

Yeah, WTF? You can’t use MSI as a generic term for an installer. It’s a very specific package format that NSIS doesn’t create. Thanks for wasting my time.

commenter
October 20th, 2009 @2:16 am  

I agree with comments above. You should change the name of the article.

commenter
Michael Said,
October 21st, 2009 @1:51 pm  

Agreed. Time to update the title of the article before this list of complaints gets any longer.

commenter
Pz Said,
November 26th, 2009 @3:19 am  

Yeah, you totally confused me, MSI is pretty problematic in NSIS, I am figuring this out at the moment. Reading your article made me think that NSIS supports it natively, which is false.

commenter
Alan Said,
December 16th, 2009 @6:28 am  

Indeed this aricle is very confusing and the information in it does not add much information to what is commonly known.

The title suggest NSIS creates MSI’s wich it can’t.

commenter
tim Said,
January 8th, 2010 @11:57 am  

Take off the msi title, it can’t do that.

commenter
Trick17 Said,
February 10th, 2010 @9:43 am  

This article is misleading. A MSI-Database has a strict format that can only be used by the MSI-Installer-Service. This Software generate a completly unique exe, that isn’t compatible with the MSI-Installer-Service. This article is wrong. /Out

Please Leave Your Comments Below

Please Note: All comments will be moderated