Version 1.00 (2014-08-12)

Now that we have obtained our code-signing certificate, we are proud to release v1.00 of the installer! Signing the installer means we endorse it as a preferred method of setting up Elixir on Windows. Having said that, we appreciate you reporting any bugs you encounter in using the installer as an issue.

Note: GitHub does not allow signed executables to be uploaded, so the executable is contained in the attached zip file.

Version 0.90 (2014-08-03)

Compared to v0.59, the installer's Programs and Features entry in the Windows Control Panel now contains publisher information. The publisher is "ElixirLang" and the publisher URL is http://elixir-lang.org/

This version can be thought of as the first release candidate. There are no more features to add or breaking changes to make, but there may be bugs which need squashing. To that end, if you do find a bug, I'd greatly appreciate you creating an issue for it.

Version 0.59 (2014-07-17)

This version reflects a change to elixir.csv and erlang.csv at elixir-lang.github.com. We've added a header row to each of them, so the installer now skips reading the headers appropriately.

Version 0.58 (2014-07-15)

This version of the installer fixes an issue where the Erlang installer would not be downloaded to the correct folder.

Version 0.57 (2014-07-11)

This installer now fixes the scenario where Erlang is installed but its entry in Path is not present. Previously, the installer wouldn't actually append Path in this case... but now it does. :)

I've also made some miscellaneous code changes which do not affect functionality. Everything else is identical to v0.56.

Version 0.56 (2014-07-11)

Compared to v0.55, the installer makes a distinction for appending Erlang's directoy to Path based on if Erlang is installed or is going to be installed. There are essentially three scenarios the installer considers.

First, if Erlang is not installed (which implies it's not in Path), the installer offers to install Erlang and then add the resulting directory to Path:

Second, if Erlang is installed, but not in Path, the installer offers to add the existing Erlang directory to Path:

Third, if Erlang is installed and in Path, no choices are offered and no Erlang-related action is taken.

In these three cases, "Erlang is installed" is defined as "There exists at least one registry key of the form HKLM\SOFTWARE\Ericsson\Erlang\#ERTSVersion# or HKLM\SOFTWARE\Wow6432Node\Ericsson\Erlang\#ERTSVersion#, where #ERTSVersion# is something like 6.1."

Finally, this release encompassed a significant refactoring of the code such that its functionality is clearer and things are easier to maintain. Having said that, soon I'll be getting around to actually commenting my code... :)

Version 0.55 (2014-07-09)

Compared to v0.54, the installer now offers to download and install Erlang and append the system's Path variable appropriately. This is implemented as a set of Inno Setup tasks with check parameters, which means that the options won't even be shown if Erlang exists.

Currently, the installer hardcodes links and names for OTP 17.1. There are several options we can explore for changing this, including:

• Reading filenames at erlang.org/download and choose the latest.
• Maintaining our own csv file (like elixir-lang.org/otp.csv) with this information and using it similar to releases.csv
• Changing nothing (releases are quite few and far between.)

Version 0.54 (2014-07-07)

Compared to v0.53, the installer now has no PowerShell dependencies, because it was discovered that the scripts are denied from running if PowerShell's execution policy wasn't changed from "Restricted" (the default) ahead of time. In particular:

• Building the installer with ISCC.exe and running it has been reverted back to entries in the [Run] section.
• scripts\extract-zip.ps1 has been removed in favor of 7-Zip
• scripts\set-env.ps1 has been removed in favor of modpath.iss. (added bonus: the directory is removed from Path when Elixir is uninstalled)

Version 0.53 (2014-07-02)

Compared to v0.52, the installer calls a new PowerShell script, scripts\make-installer.ps1, which handles the entire process of extracting the Precompiled zip archive, compiling the offline installer, and running it. This was done for two reasons:

1. Failures during any step of this process are shown and caught (whereas individual [Run] entries can't possibly keep output open or prevent subsequent entries from running if they fail.) This is helpful for me to debug problems on other people's machines.
2. Once I implement more command line arguments, the script can automate the process of building an offline installer for people who want to do that on their own.

Version 0.52 (2014-07-01)

Compared to v0.51, the installer:

• Starts with a page that asks what type of installation the user would like to perform (a radio button offering to install prereleases appears between the two below, but prereleases are not yet offered):

• Disables the finished page for the web installer and enables it for the offline installer. This means that if the web installer or the offline installer it calls fails somehow, it won't still report that Elixir installed successfully.
• Downloads and parses elixir-lang.org/releases.csv before the wizard starts, and shows an error that aborts installation if downloading fails.
• Uses a drop logo in place of the antiquated setup icon.