Carlos, You could take a look at how we do it for the Flex Installer. We build an .exe on windows and a .dmg on Mac. The code is available here: https://github.com/apache/flex-utilities/tree/master/installer
For updates, we built our own update logic. The crux can be seen here: https://github.com/apache/flex-utilities/blob/master/installer/src/com/riaspace/nativeApplicationUpdater/NativeApplicationUpdater.as Hope that helps. Thanks, Om On Tue, Jan 22, 2019 at 1:58 PM Carlos Rovira <carlosrov...@apache.org> wrote: > Hi many thanks to all for responding and expose your suggestions. > Very useful to start planing our own solution :) > > Carlos > > El mar., 22 ene. 2019 a las 21:35, After24 (<vinc...@after24.net>) > escribió: > > > Hi Carlos, > > > > We have migrated a large flex web application and choose to use the > captive > > runtime output. > > > > On mac you get a .app file that you can distribute directly or create a > > .dmg > > with the classic "drag and drop to the application folder" scenario. > > > > On Windows you get a folder that contains your app .exe and all the other > > required files. You can than create a .msi installer using WixEdit > > (tutorial > > here : > > > > > https://www.adobe.com/devnet/air/articles/customize-setup-for-AIR-app-with-captive-runtime.html > > < > > > https://www.adobe.com/devnet/air/articles/customize-setup-for-AIR-app-with-captive-runtime.html > > > > > > ) > > > > Our application is based on a shell and modules. Those modules are loaded > > locally at runtime. When an update is available, the new modules are > loaded > > from a server and the old modules are overwritten directly into the > > application folder. > > > > This solution works like a charm. > > > > > > > > > > > > > > > > > > > > -- > > Sent from: http://apache-flex-users.2333346.n4.nabble.com/ > > > > > -- > Carlos Rovira > http://about.me/carlosrovira >
