InnoSetup is very non-intrusive and flexible. The resulting installers have options for silent and very silent installation, so yes, you probably can do what you want with them. Of course, Inno and resulting setups don't do anything (or not much anyway) that can't be done from any software, but it does a nice job of putting files in known locations, updating always, only if newer, running software, etc. As an aside, it's interesting to see the term "ActiveX" *still* being used. This was something that MS was trying to kill a LONG time ago. I'm increasingly glad that I started tuning them out and focusing on the simple and reliable vs. getting wound up in every new "technology" they tried to jam down my throat. I'm much happier on Linux. But I digress. One can use Smalltalk to generate inno scripts (for a good while, I used inno to repackage MS' monthly patch madness (you had to be there...). I had code that abstracted adding files to be copied, executed, etc., or at least something like that - haven't looked at it for a few years now. With the resulting script, run the inno compiler over it, and a nicely behaved installer emerges. It was preferable to what MS was doing at the time for various reasons. And of course, one can simply write a script using Inno's or another IDE, or just a plain text editor. I took that route for installing my Dolphin-deployed executables. The script generally did a "copy if newer" type of installation, which worked well. With every update, would compile the inno scripts and send the installers on their way. The various target machines could then be told to look for and install the updates. After some nail-biting, the machines generally would re-appear on the "grid." Every so often I'd have to unstick a box, but that was rare. The real fear was hardware failures, which was the most common reason that a machine failed to return to service. Didn't happen often, but it was bad when it did. Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Igor Stasenko [siguctua@gmail.com] Sent: Saturday, April 21, 2012 5:43 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] One-click Windows comment On 21 April 2012 10:48, phil@highoctane.be <phil@highoctane.be> wrote:

Inno Setup would be a good thing to use for creating a Windows installer.

http://www.jrsoftware.org/isinfo.php

I use it regularly. Interested in a sample?

Since we're using automated builds, it is important that install packaging tools can run from command line and don't require any user interaction(s) in order to create an output. is inno installer allows to do that?

Phil

2012/4/21 Marcus Denker <marcus.denker@inria.fr>

...

On Apr 20, 2012, at 11:49 AM, Herby Vojčík wrote:

...

The ideal way would probably that .bat (or .cmd or .vbs) creates the .lnk by some ActiveX magic, runs it and quits; subseuqntly .lnk could be clicked directly.

We are planning of having installers for the three platforms... so we can make them more in the style that people expect.

But this will be done step by step and slowly (like everything :-)

For the meantime, I added a catch-all tracker for ideas how to improve the one-click:

http://code.google.com/p/pharo/issues/detail?id=5643

-- Marcus Denker -- http://marcusdenker.de

-- Philippe Back "Helping you hit the top 3 outcomes you really want to achieve"

Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil@highoctane.be | Web: http://philippeback.eu | Blog: http://philippeback.be

High Octane SPRL rue cour Boisacq 101 1301 Bierges

-- Best regards, Igor Stasenko.