Updating AIR applications

Posted by on Jun 16, 2008 in How-to, onAIR Tour | 5 comments

My presentation at the On AIR tour through Europe was about signing, deploying and updating your AIR applications. If you didn’t make it to the tour or just want to read up on these topics, I wrote three separate posts about them on the train somewhere between Prague and Munich.

This is probably the most important step to take when you are building your application and it should probably be the first thing you do. Let’s say someone found a bug in your application and you fixed it in a newer version. How are you going to tell users about that bug-fix if you don’t have an update mechanism in place? AIR has everything on board to make updating applications a breeze, both for you and the user of your application.

Signing AIR applications

Posted by on Jun 16, 2008 in How-to, onAIR Tour | Comments Off

My presentation at the On AIR tour through Europe was about signing, deploying and updating your AIR applications. If you didn’t make it to the tour or just want to read up on these topics, I wrote three separate posts about them on the train somewhere between Prague and Munich.

First of all, why is signing an application important? Easy. When your application is unsigned or signed with a self-signed certificate, the user will get two red icons on the install screen. The first one is related to your code signing certificate. It’s telling you that the “publisher is unknown” which is very normal since we have no idea who actually signed this application.

When you do get a code signing certificate and sign the application with it, the icon will turn green or in some cases yellow. The yellow icon will appear when you are using the file I/O API.