One of the biggest challenges, okay, obstacles to overcome when developing a program like LIDA to be distributed to a wide number of users is How do you PACKAGE the distribution so it’s easy for the users to install?
I’ve had to dig into researching this issue ever since we recruited our first three Alpha-version testers in December 2019, and it is NOT an easy solution.
Not only are there dozens of installer package builders out there, but in today’s environment of “fake news” and biased reviews, we always have to dig deep into all the online sources to get a good feel for the credibility of what’s being posted.
The last time before now that I used an install package builder, it was nearly two decades ago, and I used the excellent package Install Shield. It did everything I wanted to, it was easy to use, and I never had any problems with using it for clients.
So I looked them up online, found them, and checked out how much it would cost to buy it today. When I saw the prices, I ’bout had an aneurism. The version I would need costs “only” $2,899.00.
Of course, that’s for a “Perpetual License.” Hmm. The last time I bought this product was probably the year 2000, so I wonder if THAT license is still good? Naaah. They would want my old serial number, and I have no clue how to find it.
So okay, on to other installer builder packages.
I started with the one that had the most top reviews from sites I considered at least somewhat credible, and the first three programs I tried all required me to learn a new scripting language. REALLY?I spent probably two weeks poking at these, making at least semi-diligent attempts to learn their scripting language, but always came back to the “I don’t have time for this” attitude. I needed something with a wizard interface, something that NORMAL people can use.
So I then found a program called Inno Installer that does use a scripting language, but also comes with a wizard that will let you fill in the fields, then it will build the script for you, and then they have some semi-intelligible documentation that allows you to modify the script on your own so you can make it do things the wizard doesn’t provide for.That was what I have used up through the Beta version 0.9.004 release, and it served okaaaay. If it didn’t do all I wanted, at least it got the job done.
But I still wasn’t happy, especially after the v0.9.004 release wound up creating a ton of install hassles.
I thought, “Listen. An installer package should just WORK. It should not create more problems than it solves. It needs to be user friendly and handle all the issues that could arise, and do so without requiring the USERS – the people installing the software – to be computer geeks.”
On top of this, it turns out that installing programs that run on MSAccess, which LIDA is, have an additional set of install issues not usually present with other programs.
Knowing I wasn’t totally happy with Inno Installer, I had already been posting cries for help on various forums, and in one of the replies by a person who turns out to be a Microsoft MVP (not sure exactly what that is), was a reference to a website with a review of installer builders, and on that website was a reference to a builder I’d not yet heard of.
Whew! What a convoluted way to get to the whole point of this post!
It turns out this new to me installer builder program – SSE Setup – addressed ALL but one of the installer issues we’ve encountered with LIDA, so I downloaded it and have been studying the documentation, all day yesterday (among solving computer issues and corresponding with beta testers), and today I’m going to practice building the new installer package, and with the next upgrade to LIDA, whichever the Beta release version is that comes after 0.9.004, it will be with this hopefully excellent new installer builder program.I definitely have my fingers crossed that this package will solve most if not all the LIDA install issues. We will see what happens.