Update: this post has the answer for this first part: http://forums.adobe.com/message/4687256#4687256
The version number that shows up in Adobe Extension Manager is controlled in the .mxi file.
<macromedia-extension name="com.zaalabs.MyExtension" requires-restart="true" version="1.2.3">
I haven't found a way yet to pull the version number directly from the MXI file at runtime to show in an about window. To work around this we actually populate the version number in two places using an ANT script.
One in MyExtensionVersion.as which gets compiled in and can be looked up at runtime, and then other in the MXI file.
public class MyExtensionVersion
// This will be populated from the MyExtensionVersion.as.template
public static const VERSION_NUMBER:String = "1.2.3";
Then in our application we can lookup MyExtensionVersion.VERSION_NUMBER
Message was edited by: Nate Beck
Sorry for the double post.
I forgot to answer your update question.
You can also add the following to your mxi file.
That should point to an XML file at that url which has the folloiwing information.
<ExtensionUpdateInformation> <version>1.2.3</version> <download>http://example.com/MyExtension.zxp </download> <description url="http://example.com/description.html"> <![CDATA[Some description ]]> </description> </ExtensionUpdateInformation>
This is helpful because it allows users to update directly from Adobe Extension Manager by clicking an "Update" button.
Also, please be aware that Adobe Extension Manager will prompt a user to update if the version number diverges at all. For example, if my installed version is 2.0.0 but the update xml on my server says 1.0.0, Adobe Extension Manager will tell the user there is an update available, even though we think of 2.0.0 as newer than 1.0.0.
Thanks, I'm a bit confused now, which file you mean with ".mxi" ?
Regarding the post in the link you provide it should be read from the manifest.xml file, no doubt it works but may be easier for my purpose just to add a variable to control the version.
Ah.... sorry the MXI file is included when you create a hybrid plugin. Looks like you just need the manifest file.
Thanks, now I understand
Will try to implement this updating method, but not sure if it will be the best regarding that there is no control of users and versions because the update is processed by the extension manager directly.
There is no way to know if the user is elegible for an udpate of a commercial extension.