Recently a great dev (you know who you are, thank you!)
made me aware of a great post back in March 2018
One of the great things about the Desktop Bridge is that it’s provided new distribution channels - the Microsoft Store, Microsoft Store for Business, and the Microsoft Store for Education for software developers that up until the introduction of the Bridge, have had to rewrite their applications for UWP or not participate in Store. On the App Consult team, we have assisted Desktop Bridge developers using the plethora of Win32 runtimes: WPF, MFC, Windows Forms, VB.Net, Adobe Air as well as more esoteric runtimes like Electron, Java, and Flash with the MDM Zinc runtime (Google it with Bing!).
Adobe Air is a popular cross-platform runtime. Like most runtime environments, the Air runtime is updated separately from the application. No doubt, you’ve experienced the update prompt when starting an Adobe Air application. This introduces a complication when creating a Windows Store app using the Desktop App Converter. That is, while the app update is handled by the Store, the runtime is not. One solution is to do a chained DAC conversion of the runtime and the application. See this blog post for more information on chained installer conversions.
While a chained DAC conversion works well for some dependency scenarios, a better solution for Adobe Air apps is to package them as a captive runtime bundle. This packaging eliminates the issues with Air runtime updates since the runtime is packaged along with the app. See here for a full list of the benefits and drawbacks of this approach. After you’ve created the captive runtime bundle, you can do a Desktop App Converter manual conversion to package the application into an APPX file. See here for information on doing a manual DAC conversion.
Using Adobe’s captive runtime bundle to package your Adobe Air apps will make your DAC conversions much easier!
More useful Desktop Bridge info here: Best Practices for Packaging and Common Issues for Desktop Bridge Apps!
How do you like that ?
That’s a 10+ years Microsoft employee telling you how much Adobe AIR is popular
and how easy it is to convert it with Desktop Bridge.
But it does not stop here, as you can see this post is posted on that blog
App Consult Team Blog
The Windows App Consult team blog for the latest updates on events and technical articles, success stories and team public updates.
For those who don’t know, a “consult team” or “consultant team” is a team of developers working for the vendor (this time Microsoft) and who assists customers trying to use products and services of that said vendor but facing integration difficulties.
And when those guys post stuff it is in general a treasure trove because they are really knowing their stuff from the inside out and in general explains it in a way “here let me show you how it would work if you program it this way”.
So if you look into the archives of this blog, yep, you can find very useful and informative stuff that are developers oriented.
Here few of those
Using Windows Universal Runtime APIs from a standard Unity executable
Ok it is Unity, but you can apply the very same stuff to ANE for AIR, and those infos lead to more infos
Package Support Framework
The Package Support Framework (PSF) is a kit for applying compatibility fixes to packaged desktop applications.
- Package Support Framework
So not all those posts are directly about AIR but if you can load a .NET DLL from Unity you can do the exact same thing from an ANE, it is quite easy to adapt the example to your own need.
And while we are on the topic, check out also that other post
Part I: From Air to Windows Store
We have recently released our first game for Windows 10 on the Windows store, including in-app purchases. Since there are only few resources available how to convert an app to a Windows Universal Package (UWP), especially from an Air perspective, I want to share a step-by-step guide. This first part will cover the conversion of a generic Air app to the Windows store. I plan to write a second part that explains how to include in-app purchases, since that part is quite complex.
which is also full of good informations
All of that should help if you want to publish your AIR app to the Windows store .