Building a Proper Windows Installer

 

Building a Proper Windows Installer for Vexon (Behind the Scenes)

When software starts to grow beyond simple scripts and into something users rely on, packaging becomes just as important as the code itself. For Vexon, we wanted an installer that felt native, behaved consistently, and required zero configuration from the user. That’s exactly what the Vexon Installer achieves.

In this post, we explore what the installer does, why it’s built this way, and how it makes Vexon feel like a real, first–class programming language on Windows.

---

Why Vexon Needed a Real Installer

Originally, running Vexon meant manually placing files somewhere and typing out long Node commands like:

node vexon_cli.js run example.vx

That works for development — not for users.

We needed:

• A fixed installation directory (C:\Vexon)

• Automatic PATH support so you can run vx from any terminal

• A .vx file association so you can double-click Vexon source files

• A proper uninstall entry in Control Panel

• A minimal, stable installer with no external dependencies

The final result is a small, fast, reliable installer that behaves exactly like installers for mainstream languages and tools.

---

What the Installer Does (Step by Step)

1. Installs Everything in C:\Vexon

The installer places all core files in a single clean directory:

• vexon_cli.js

• vexon_core.js

• version.txt

• Vexon icon

• A small vx.bat launcher

Because the install path is constant, support tools and scripts can rely on it.

---

2. Creates a vx Command You Can Run Anywhere

To run Vexon easily, the installer writes a simple launcher:

vx example.vx

Under the hood this just calls:

node C:\Vexon\vexon_cli.js run <file>

Then the installer appends C:\Vexon to your system PATH.
After a reboot, any terminal can use the vx command instantly.

---

3. Adds File Association for .vx Files

Double-clicking a .vx file automatically runs:

vx "<file>"

This means Vexon behaves like a true scripting language on Windows — opening a source file isn’t just editing it, but actually running it.

---

4. Registers a Full Uninstaller

The installer adds a clean entry in:

Control Panel → Programs and Features

Uninstalling will:

• remove file associations

• remove Vexon from PATH

• delete all installed files

• remove the installation directory

• remove the uninstall entry itself

This ensures Windows does not keep stale paths or registry keys.

---

5. Cleans Up PATH Safely on Uninstall

Most installers append paths, but few properly remove them.

The Vexon Installer includes a safe mechanism to remove C:\Vexon from the PATH even if users edited PATH manually or the directory appears more than once.

The result:
No broken PATH entries.
No polluted environment variables.
No leftover clutter.

---

Why This Installer Is Special

Most simple installers only copy files. The Vexon installer does a lot more:

Feature	Included
Custom installation directory	✔ (C:\Vexon)
Global PATH integration	✔
.vx file association	✔
Clean uninstaller	✔
Safe PATH cleanup	✔
Small file size (lzma compression)	✔
Works on all modern Windows versions	✔

The goal was reliability above all else — nothing fancy, nothing unstable.
Just a professional-grade installer for a professional-grade tool.

---

The User Experience

Here’s what installing Vexon feels like:

1. Run the installer .exe

2. Choose the installation directory (or accept C:\Vexon)

3. Click Install

4. Reboot (Windows requires this to update PATH)

5. Open any terminal and type:

vx

You’re ready to code.

---

Why We Didn’t Use MSI or Electron Installers

Many modern installers are bloated. MSI is complex, and Electron-based installers can exceed 100 MB.

NSIS (the technology behind this installer):

• is tiny

• is proven and stable

• supports full scripting

• works even on older Windows

• gives total control over registry, PATH, and file associations

For a programming language like Vexon, lightweight and predictable behavior is more important than fancy UI.

---

Final Thoughts

The Vexon Installer is part of a bigger goal: making Vexon feel like a serious, accessible, and user-friendly language. Small touches — PATH integration, file associations, clean uninstall — go a long way in making a tool feel professional.

This installer ensures that anyone can get up and running with Vexon in seconds, without friction, confusion, or technical setup.

Get the full pack here.