MSI for installation
Sorry to ressurect such an old thread, but the responses here are...subpar.
Absolutly not (unless it was an alternative install package.) IMHO, MSI sucks.
Coming from someone with the username "Guests", they seem to be speaking for the entire project. Who cares if MSI sucks, so does Windows. I still have to use it, and I still have to deploy this software. Instead of using a proper method though, I have to use a hacked-together conglomeration of scripts, or use a third party program to distribute the software, which is not easily trackable. This does not allow for good management of the software. Additionally, with how simple the installer is, any additional features provided by NSIS seem unneccesary.
But beyond that AHK is a nice, simple program that only requires only autohotkey.exe to run any script and leaves no footprint of any kind when the .exe and .ahk files are deleted - a very much in demand behaviour for many (most ?) users.
Yes, to run a simple script, that is all that is required. To be able to run scripts consistently, the program must be installed, and associated with the ahk filetype, or else I'll have to select the exe every time I want to launch a new script. These are things that are solved by having an installer that fits in with the Microsoft ecosystem on which the program runs.
If anyone could please chime in on this, since this thread was from 6 years ago, I imagine that attitudes may have changed. MSI isn't going anywhere, and would be super-useful to be able to accountably deploy this software in a domain environment.
Forgive my ignorance, but I'm confused in where exactly the problem lies. When I look at "Programs and Features" to uninstall, AutoHotkey is there. Also, when an .ahk file is right-clicked, to "run" or "edit" the file options show.
Files can also be run as compiled from the server, or the autohotkey.exe and scripts sit on a specified folder on the workstations. If it's a logon script, from the domain controller, we would use the directory that corresponds to the domain controller's Netlogon shared folder (SystemRoot\SYSVOL\Sysvol\DomainName\Scripts).
Why not NSIS, as opposed to MSI, because aren't they accomplishing the same thing? And there is an open-source option to create .msi called WiX, http://wixtoolset.org/. Though it's supposed to be a monster to learn and not suited for everyone, but Microsoft uses it too.
Perhaps an explanation of your situation (like if using XP workstations, etc...) can clarify why MSI is needed and other solutions aren't acceptable. Like if MSI is better for network wide installation of AutoHotkey.
AutoHotkey v1.1 doesn't use NSIS for its installer.
Additionally, with how simple the installer is, any additional features provided by NSIS seem unneccesary.
I have no idea what you mean by "accountably deploy". Unattended installations (including upgrade installations) of AutoHotkey are extremely simple; just run the installer with a simple command line switch.
MSI isn't going anywhere, and would be super-useful to be able to accountably deploy this software in a domain environment.
Might be worth mentioning that WinZip and PeaZip have self-extractors in the form of .exe. This can be used as a quasi-installer on computers in a network. Just load all the files up in the self-extracting zip, including any .bat files, and distribute from the netlogon shared folder. Even if you are running around by foot doing installs, can put on a usb drive, and install by a single double-click if the self-extracting zip/.exe is setup properly.