ZigMeowNyan

Ok, I'm looking into how to best install Node from an external MSI at the moment. There's a lot of ways this type of thing can be handled, and I...

> > The installer needs to a) bundle Node (another MSI), and if it doesn't exist, run that installer first, and b) place the bundled cash package in a directory,...

I'm going to check through the UI templates for one that fits the feature selection UX. I should have a simple example for you within 15-30.

[Here's an example](https://gist.github.com/ZigMeowNyan/7d11bc1c2c94f83b69a6) that provides a feature selection with two components: ls.exe and dir.exe. This should give you an idea of how it works. Since I didn't know if you...

> Okay great. Now the tricky part is that ls, dir, etc. aren't going to be .exes. This part is just for file deployment, and works for any file type....

Yeah, Wix# is pretty handy. You don't have to know the XML config, but then you've got to know C# and have a .NET build environment ready, which might not...

@dthree I had to do some other stuff, but I finished and put together a [gist](https://gist.github.com/ZigMeowNyan/57e0e9605979da272c68) for a bootstrapper that installs Node if they're running anything less than 5.7.0 (the...

@dthree I did some thinking about the configuration aspect. It seems to me that the simplest approach to translating feature configuration to configuration in a script is by [writing to...

@dthree No problem. It _has_ hit 3.4K stars in 4 days, so I expect it's kept you quite busy. Just tackle it at your own pace, and drop a mention...

Thank you very much for your quick response. From the user perspective, it should be `make.exe`. We're hoping to change the final binary that runs in their environment when they...