Skip navigation
MSSDedalus
MSSDedalus
Currently Being Moderated

Version number and updating extension

Sep 5, 2012 8:24 AM

I wonder where to set my application version number, I have tried at the bundle manifest but if setting at extension it is not shown anywhere at the extension manager and I don't know how to get this value for an "About" window.

 

Therefore I have set the bundle version to match my application number, this way at least the number is visible in the manager.

 

Also if I try to install an updated version of my extension the extension manager asks me to delete previous version because it conflicts with this one, I expected that the extension manager would ask if updating; am I doing something the wrong way ?

457 Views   5 Replies   Latest reply: MSSDedalus, Sep 10, 2012 11:25 AM
 
Replies
  • Nate Beck
    Currently Being Moderated
    1. Nate Beck,
    Sep 10, 2012 10:49 AM   in reply to MSSDedalus
    Report

    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.

     

    package

    {

              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

     
    |
    Mark as:
  • Nate Beck
    Currently Being Moderated
    2. Nate Beck,
    Sep 10, 2012 10:47 AM   in reply to MSSDedalus
    Report

    Sorry for the double post.

     

    I forgot to answer your update question.

     

    You can also add the following to your mxi file.

     

    <update url="http://example.com/update.xml"/>

     

    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.

     
    |
    Mark as:
  • MSSDedalus
    Currently Being Moderated
    3. MSSDedalus,
    Sep 10, 2012 11:04 AM   in reply to Nate Beck
    Report

    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.

     
    |
    Mark as:
  • Nate Beck
    Currently Being Moderated
    4. Nate Beck,
    Sep 10, 2012 11:10 AM   in reply to MSSDedalus
    Report

    Ah.... sorry the MXI file is included when you create a hybrid plugin.  Looks like you just need the manifest file.

     
    |
    Mark as:
  • MSSDedalus
    Currently Being Moderated
    5. MSSDedalus,
    Sep 10, 2012 11:25 AM   in reply to Nate Beck
    Report

    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.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points