1 person found this helpful
1: We are working on a method to use a local socket to communicate with an installed c# application on the users machine. The situation is very similar, however we store credentials encrypted and accessible to the installed binary. If those credentials do not exist the AIR app requests the user to input them and they are sent to the binary. These credentials are stored either per session, daily or forever per the user's preferences. We use this method to let AIR be the front end it was designed to be and leave all the heavy lifting OS / processor wise to the binary. Unsure if this would help but you can read a bit more on using local sockets here: http://help.adobe.com/en_US/AIR/1.5/devappshtml/WS5b3ccc516d4fbf351e63e3d118666ade46-7caf. html
2: The EULA is still required as the End User has to accept it. If there's a way around that, I'm not aware.
3: The installation directory can be changed by the user unless you are performing silent installs (available when you sign a redistribution agreement). I don't recommend relying on the installation directory never changing.
var file = air.File.applicationDirectory.resolvePath("testfile.html");
//application storage directory
var file = air.File.applicationStorageDirectory.resolvePath("testfile.html");
4: I've faced the problem where the AIR runtime is not available, but we always fall back on the badge there. For what it's worth it's pretty handy at detecting requirements and getting them to the user.
hope that helps
Hi there Jason - thanks for the reply. I think I'll apply for a redistributon license and see how I get on.