IMatch 5.4.10

[jelvers]

Just short feedback: Smooth installation as always and no issues so far.

Rgds, Juergen

[Mario]

Thanks.

[ianrr]

Same here  ... smooth install and program feels very stable.

Ian

[BanjoTom]

+1

[Photon]

Even the update over existing installations always worked perfect and very fast during my last "felt 50" IMatch updates!
And even with an installation path which is different from the ugly default of Windows.

Reason for another installation path for all my SW is, that I urgently need path names without spaces. This because simple hyperlinks like "file:///c:/Program Files/..." or copy/paste paths will not work automatically in advanced text editors and other tools when spaces and other special symbols are used. The workaround to replace e.g. space " " with "%20" or to use e.g. "PROGRA~1" is not convenient and sometimes not working.

A minor improvement could be that the IMatch installer does detect the installation path of previous installed version and does use this as default value.

Regards, Martin

[Mario]

A minor improvement could be that the IMatch installer does detect the installation path of previous installed version and does use this as default value.

This would require me to:

A) Buy a 'pro' version of the installer tool: US$1000 + 500 US$ per year maintenance. I currently use the standard version, which is part of Visual Studio and thus covered by the annual fee I pay to Microsoft.
Even when I buy the pro version, thinks like you suggest requires my to learn about the programming interface of the installer, implement code in a separate DLL and make all this work. Doable, but complex.

- or-

B) Switch to another (free) install tool, learn it, learn about all quirks and gotchas and how to work around it. Face all the dreaded "Does not install on my machine" error messages again etc.  Lean how to implement the suggest functionality etc. The documentation is almost 300 pages...


How many users do you think don't install applications into the designed folder? I would guess something < 5%.
You can always work around the "ugly" folder name (I assume here you mean the blank in "Program Files") by using %PROGRAMFILES%. In Germany, "Program Files" is actually named "Programme", so no blank 

[Carlo Didier]

... will not work automatically in advanced text editors and other tools when spaces and other special symbols are used...

I don't think they are advanced if they can't cope with spaces in file names or paths, which have been around for very long now and are pretty much standard. For a long time now, I haven't had any "space"-related problems for years.

You already mentioned one possibility with Progra~1 (haven't used that since the days of Win98). You could also create a mapping or a junction for use with your problematic software. That would allow you to stay with the standards and only use a workaround for the one problematic software. Over the years in as an IT professional, I've learned that it's always better to try to adapt (or "dupe") the software that doesn't comply to standards than to try to bend the standards and risk problems or at least complications with all other software.