Some days you've just gotta work on something fun
-
I've been buried in legacy maintenance of other people's 💩 for a while, to the point where I really don't want to come in to work :sigh:. Among other things I do our installers, which encapsulate several third-party packages. Today, we've discovered a problem that's fixed in a new version of a package. The new package requires that the old one be uninstalled before the new one goes in. While this isn't too hard, the uninstaller isn't silent and the user has to click on a number of buttons for it to do its thing. Here's the fun part. For a long while I've wanted to have my installer click buttons automatically so that I didn't have to rely on the user doing it. Even when I include detailed and explicit instructions in my installer, they sometimes screw it up. We use Inno Setup[^] which lets you call functions in a DLL of your own from their Pascal script. I use this feature for several things that aren't easily accessible from script. I'm implementing an auto-click feature in the DLL that spins up a thread that watches for windows with a caption and then clicks a specified button in that window. It looks like it's going to work. I'm happier than a pig in slop :jig:.
Software Zen:
delete this; -
I've been buried in legacy maintenance of other people's 💩 for a while, to the point where I really don't want to come in to work :sigh:. Among other things I do our installers, which encapsulate several third-party packages. Today, we've discovered a problem that's fixed in a new version of a package. The new package requires that the old one be uninstalled before the new one goes in. While this isn't too hard, the uninstaller isn't silent and the user has to click on a number of buttons for it to do its thing. Here's the fun part. For a long while I've wanted to have my installer click buttons automatically so that I didn't have to rely on the user doing it. Even when I include detailed and explicit instructions in my installer, they sometimes screw it up. We use Inno Setup[^] which lets you call functions in a DLL of your own from their Pascal script. I use this feature for several things that aren't easily accessible from script. I'm implementing an auto-click feature in the DLL that spins up a thread that watches for windows with a caption and then clicks a specified button in that window. It looks like it's going to work. I'm happier than a pig in slop :jig:.
Software Zen:
delete this;I used to rip apart MSI files with some MSI decompiler thing that I used to have, and then modify them to make them unattended. I wish I could remember the tool name. Orca or something?
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
But according to the docs, InnoSetup does also understand the command line Parameters /SILENT and /VERSILENT. They did not work for you?
This is the case where the encapsulated installers don't support silent installs or uninstalls. I even have one case where a command line installer when run with the silent option still pops up a message box when it completes :rolleyes: :mad:.
Software Zen:
delete this; -
I used to rip apart MSI files with some MSI decompiler thing that I used to have, and then modify them to make them unattended. I wish I could remember the tool name. Orca or something?
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
MSI is an abomination before all known deities. Before we started using Inno Setup we tried InstallShield, which generated MSI. I spent over a month trying to get our stuff installed properly. When I found out they wanted over $1K for each additional user language to support localized installs, I said screw it and went looking. After finding Inno Setup, I replicated our product install in in a single day.
Software Zen:
delete this; -
I used to rip apart MSI files with some MSI decompiler thing that I used to have, and then modify them to make them unattended. I wish I could remember the tool name. Orca or something?
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
Orca rings a bell, yes.
-
I used to rip apart MSI files with some MSI decompiler thing that I used to have, and then modify them to make them unattended. I wish I could remember the tool name. Orca or something?
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
It was indeed called Orca, and was part of the Platform SDK. A few links brought me here: [Windows SDK - Windows app development | Microsoft Developer](https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/) There's no direct link to it however, it looks like you have to download the entire SDK just to get that one file. [Edit] Oh, and [here](https://learn.microsoft.com/en-us/windows/win32/msi/orca-exe). Although this still has no direct link.
-
I've been buried in legacy maintenance of other people's 💩 for a while, to the point where I really don't want to come in to work :sigh:. Among other things I do our installers, which encapsulate several third-party packages. Today, we've discovered a problem that's fixed in a new version of a package. The new package requires that the old one be uninstalled before the new one goes in. While this isn't too hard, the uninstaller isn't silent and the user has to click on a number of buttons for it to do its thing. Here's the fun part. For a long while I've wanted to have my installer click buttons automatically so that I didn't have to rely on the user doing it. Even when I include detailed and explicit instructions in my installer, they sometimes screw it up. We use Inno Setup[^] which lets you call functions in a DLL of your own from their Pascal script. I use this feature for several things that aren't easily accessible from script. I'm implementing an auto-click feature in the DLL that spins up a thread that watches for windows with a caption and then clicks a specified button in that window. It looks like it's going to work. I'm happier than a pig in slop :jig:.
Software Zen:
delete this; -
I used to rip apart MSI files with some MSI decompiler thing that I used to have, and then modify them to make them unattended. I wish I could remember the tool name. Orca or something?
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
Yes, it's Orca. But that's like doing assembly programing. I wouldn't wish it on my favorite enemy.
Bond Keep all things as simple as possible, but no simpler. -said someone, somewhere
I don't remember it being terrible for modifying MSIs as long as you knew how they worked, but I wouldn't use it to build one from scratch.
Check out my IoT graphics library here: https://honeythecodewitch.com/gfx And my IoT UI/User Experience library here: https://honeythecodewitch.com/uix
-
I've been buried in legacy maintenance of other people's 💩 for a while, to the point where I really don't want to come in to work :sigh:. Among other things I do our installers, which encapsulate several third-party packages. Today, we've discovered a problem that's fixed in a new version of a package. The new package requires that the old one be uninstalled before the new one goes in. While this isn't too hard, the uninstaller isn't silent and the user has to click on a number of buttons for it to do its thing. Here's the fun part. For a long while I've wanted to have my installer click buttons automatically so that I didn't have to rely on the user doing it. Even when I include detailed and explicit instructions in my installer, they sometimes screw it up. We use Inno Setup[^] which lets you call functions in a DLL of your own from their Pascal script. I use this feature for several things that aren't easily accessible from script. I'm implementing an auto-click feature in the DLL that spins up a thread that watches for windows with a caption and then clicks a specified button in that window. It looks like it's going to work. I'm happier than a pig in slop :jig:.
Software Zen:
delete this; -
I've been buried in legacy maintenance of other people's 💩 for a while, to the point where I really don't want to come in to work :sigh:. Among other things I do our installers, which encapsulate several third-party packages. Today, we've discovered a problem that's fixed in a new version of a package. The new package requires that the old one be uninstalled before the new one goes in. While this isn't too hard, the uninstaller isn't silent and the user has to click on a number of buttons for it to do its thing. Here's the fun part. For a long while I've wanted to have my installer click buttons automatically so that I didn't have to rely on the user doing it. Even when I include detailed and explicit instructions in my installer, they sometimes screw it up. We use Inno Setup[^] which lets you call functions in a DLL of your own from their Pascal script. I use this feature for several things that aren't easily accessible from script. I'm implementing an auto-click feature in the DLL that spins up a thread that watches for windows with a caption and then clicks a specified button in that window. It looks like it's going to work. I'm happier than a pig in slop :jig:.
Software Zen:
delete this;I got into that installer crap a long while ago when MS rolled out their new approach. I'd rather stick needles in my eyes. That said, it appears I need to make $$ again, so ....
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Gary Wheeler wrote:
I'm implementing an auto-click feature in the DLL that spins up a thread that watches for windows with a caption
Autoit? https://www.autoitscript.com/site/[^]
Unfortunately the corporate IT gestapo gives me a load of crap every time I want to use third-party software. For open source / freeware I just use it and beg forgiveness if I get caught. This is what happened when they discovered I was using Inno Setup. They wanted me to stop using it, but by that time it had been used for all of our products for years. Purchased software is a PITA because they evaluate it, don't like it, and then offer an alternative that doesn't do what I need. For this reason, I usually roll my own for this sort of thing.
Software Zen:
delete this;