We got NSIS, an IDE and we know we shall write some instructions to create an installer. Personally, I didn't learn to use NSIS scripts until I started creating my own instructions from scratch. We have a wizard, a page designer and also, F1 launches the NSIS Script CHM help file.Īfter running the IDE, you can either type in commands or use the wizard to create a template for a simple installer. In the HM editor, we can also compile and run our installers without the need to exit the IDE. Here's a link to the available text editors page. It's not quite bad, but it's much better to have an IDE, isn't it? The second link above refers to a good yet small IDE for NSIS called 'HM NIS Edit.' In the NSIS Developer Center, you can download other IDEs or integrations to current Editors like Eclipse. Compiling a ScriptĪfter downloading and installing NSIS using the link provided above, all we need to do is create a new text file called WhatEverName.nsi, type down our commands, right click on the file and select 'Compile NSIS Script.' Then we ask the NSIS compiler to compile the file and create a setup executable file. The idea is that we create a single (or multiple) file(s) that contain(s) the script instructions. To create a simple installer with NSIS, we should start learning the NSIS scripting language. I put a link to those I used in this article here: Beside the NSIS compiler comes a lot of handy tools and plug-ins, mostly written by the NSIS community.

In the final lab, we will have a complete setup application.īefore starting NSIS, we first need to get its compiler. In each lab, we will examine a bit more than what we talked about in that part. Labs come at the end of each part of this article. This article introduces NSIS and shows how to create a simple setup application using powerful, yet easy, NSIS scripts. The second one was NSIS and since I learned it, I did not go further. There are many tools to create an Installer for our applications.

Nsis package switches