Hi Josh, I always find using MSIs troublesome, maybe maybe the approach below is also of use to you. I take advantage of the fact that Node on Windows is just a single .exe and doesn't need installing, so I make use it as a portable app.
I create individual application folders, which contain their own copy of a specific (tried and tested) version of Node, and the JS application I want to distribute. I zip the entire folder structure, and provide my remote partners with the portable package and a batchfile to do the unpacking. The batchfile can unpack the entire package in a subfolder in the user's profile folder (in batch, variable %userprofile% gives you the root folder of the user"s envrionment, so this is writable). In an accompanying VBscript, you can create/remove shortcuts on the desktop (the WshShell.CreateShortcut method, see http://msdn.microsoft.com/en-us/library/xsy6k3ys(v=vs.85).aspx) Of course, you are finally left with the problem of poking a hole in the local firewall for your listening webserver, if necessary. When I need to provide them with updated NPM packages or another version of node.exe I simply send them another .zip, complying to the original folder structure. Kind regards, Eelco -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
