How to use the Windows Deployment Tool
pmulroney at logicaldevelopments.com.au
Fri Jul 29 00:26:47 UTC 2022
On windows we use Inno setup - you could take the folder that's produced by the Windows Tool, add desktop shortcut, The 2015 redistributable, any other components that you want to add outside the application, include code signing, and Inno Setup creates the installer that does all that.
On mac, we wrote a bunch of scripts to assemble, code-sign, etc, and then use Packages to create the installer. This was before the deployment tool was created. The deployment tool assumes that you'll create a .dmg file and people will drag/drop the app onto the applications folder. We wanted a little more control over the install process, so we used Packages, which allows us to have postflight scripts to create shortcuts, install services etc. on the Mac.
> On 29 Jul 2022, at 2:36 am, Mike Matthews - Omnis via omnisdev-en <omnisdev-en at lists.omnis-dev.com> wrote:
> I use the Windows tool supplied by Omnis. It works well, we add xComps, icons, folder paths, etc. The one thing it doesn’t do, is to make it an installer, where you can install the Microsoft Visual C++ 2015 Redistributables, etc. Add things like a desktop shortcut, task bar icon, we use something else to do that. Can’t remember the name of it though, Reuben does that part.
> I still use Terminal to customise and notarise on OSX, as it all works.
> But to add silent PG install, well if it can be done silently, then I’ll like to know more about how to that, Mac & Windows.
> Mike Matthews
> Lineal Software Solutions
> Commercial House, The Strand<x-apple-data-detectors://1/1> Barnstaple, Devon, EX31 1EU<x-apple-data-detectors://1/1>
> omnis at lineal.co.uk<mailto:mike.matthews at lineal.co.uk>
> On 28 Jul 2022, at 15:58, Michael Houlberg <michael at houlbergdevelopment.com<mailto:michael at houlbergdevelopment.com>> wrote:
> I’m experimenting with the Deployment Tool for Windows in Omnis 10.2 31315. The docs are pretty thin, but I think I have it working. It seems pretty simple. I’m pretty much just adding a library to the startup folder and changing the application name. I point it to an output folder which creates a folder with all the runtime components including a firstruninstall folder. The tree looks correct, but I thought I was going to get something I can send to a client to install on their computer.
> Like, shouldn’t I be able to generate either an .exe or a .msi? How do you use the result of the deployment tool to actually deploy your application?
"Doc, I can't stop singing 'The Green Green Grass of Home'."
"That sounds like Tom Jones Syndrome"
"Is it common?"
"Well, It's Not Unusual…"
Paul W. Mulroney We Don't Do Simple Pty Ltd
pmulroney at logicaldevelopments.com.au Trading as Logical Developments
www.logicaldevelopments.com.au ACN 161 009 374
Ph: +61 8 9458 3889 86 Coolgardie Street
BENTLEY WA 6102
More information about the omnisdev-en