Quantcast
Channel: Adobe Community : Unanswered Discussions - AIR Development
Viewing all articles
Browse latest Browse all 2010

extendedDesktop profile

$
0
0

Hello,

 

I'm wokring on an AIR app for Windows that uses native extensions. To do so, I need to use extendedDesktop profile, but I cannot compile .AIR file using only that - it requires a native installer. However, I'm unable to compile native installer .EXE because I'm using Linux to do automated builds. So I've added this to my descriptor:

 

<supportedProfiles>extendedDesktop desktop</supportedProfiles>

 

This way I can get it compiled and signed into an .AIR file. After I install this app on the target machine with Windows 7 - the application is being launched with desktop profile (I suppose so, because native extensions do not work). However, if I launch that installed application with ADL debugger - it uses the first profile from the list, which is extendedDesktop and my native extensions work fine. Is there a way to force launch the app with extendedDesktop without ADL? I know, documentation says that to have native extensions I MUST package it into a native installer, but I didn't do it and the compiled, packaged and installed app can work with native extenstions if I run it with ADL. I suppose I don't understand something, I'm very new to this. Does ADL provide something needed for extendedDesktop and this something is only included with the app if I package it into native installer? So since I've packaged it in .AIR - only ADL can provide this something? Can I get .EXE package on Linux somehow? I'm using Maven for automated builds and this whole thing seems unreasonbly tangled to me


Viewing all articles
Browse latest Browse all 2010

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>