×

Discussion Board

Page 2 of 2 FirstFirst 12
Results 16 to 24 of 24
  1. #16
    Regular Contributor
    Join Date
    Aug 2012
    Location
    Rhine Valley
    Posts
    93

    Re: Distinguishing published app from development version

    I found a relatively simple solution when going via the app list:

    When opening the context menu for the app, the in-store version has the 'review' menu item while the sideloaded version doesn't.

  2. #17
    Registered User
    Join Date
    Dec 2012
    Location
    Zagreb, Croatia
    Posts
    73

    Re: Distinguishing published app from development version

    But that incurs an additional overhead. You want to differentiate them at a glance, either from name or an icon.

  3. #18
    Registered User
    Join Date
    Jan 2009
    Location
    Melbourne, Australia
    Posts
    2,571

    Re: Distinguishing published app from development version

    Quote Originally Posted by influencer View Post
    I found a relatively simple solution when going via the app list:

    When opening the context menu for the app, the in-store version has the 'review' menu item while the sideloaded version doesn't.
    That is simple.

    In your opinion, is there still benefit to documenting the other solutions - perhaps more "generically" rather than as meeting this particular use case?

  4. #19
    Regular Contributor
    Join Date
    Aug 2012
    Location
    Rhine Valley
    Posts
    93

    Re: Distinguishing published app from development version

    Yes, in my opinion an article showing the pros and cons of the various ideas would be great.

  5. #20
    Regular Contributor
    Join Date
    Aug 2012
    Location
    Rhine Valley
    Posts
    93

    Re: Distinguishing published app from development version

    Now,
    the next step on the ladder:

    I now have 3 apps on my phone with the same name...

    First, the published version of my app (1.9).

    Then, the WP7 next version (1.10).

    Last but not least, the WP8 Version of the next incarnation (2.0).

    Now the differentiation gets a bit more difficult again. Both debugging versions don't have a 'review' menu entry. The sequence in the app list is not deterministic, now the published version is on top. Currently I have no other way than to open the about page in the app to find the version number.

    I might integrate the version number into the application icon, but that's a lot of work, too.

    An article about this gets more and more interesting...

  6. #21
    Nokia Developer Champion
    Join Date
    Feb 2013
    Location
    Dublin, Ireland
    Posts
    573

    Re: Distinguishing published app from development version

    I'll get started on an article this week.

    Are your WP7 and WP8 versions of your app on different solutions?

  7. #22
    Regular Contributor
    Join Date
    Aug 2012
    Location
    Rhine Valley
    Posts
    93

    Re: Distinguishing published app from development version

    No, but I found out the reason. The WP7 and WP8 versions have different GUID (given by VS). I didn't yet synchonize them because I read that the store adapts the GUID when submitting.

    Nevertheless today I wrote the WP7 GUID into the WP8 WMAppManifest.xml.

    Now, if I first deploy my WP7 app to the device and add some state, I can later deploy the WP8 version and it updates the app from 7 to 8. The state (iso store) is preserved, so I can test if the upgrade preserves my settings.

    This I find rather helpful.

    Thomas

  8. #23
    Nokia Developer Champion
    Join Date
    Feb 2013
    Location
    Dublin, Ireland
    Posts
    573

    Re: Distinguishing published app from development version

    Quote Originally Posted by influencer View Post
    No, but I found out the reason. The WP7 and WP8 versions have different GUID (given by VS). I didn't yet synchonize them because I read that the store adapts the GUID when submitting.

    Nevertheless today I wrote the WP7 GUID into the WP8 WMAppManifest.xml.

    Now, if I first deploy my WP7 app to the device and add some state, I can later deploy the WP8 version and it updates the app from 7 to 8. The state (iso store) is preserved, so I can test if the upgrade preserves my settings.
    There was a post a few months back on the Windows Phone Developer blog which talks about submitting a WP7 and WP8 version of an app and how GUIDs work in that case...

    http://blogs.windows.com/windows_pho...s-phone-8.aspx

  9. #24
    Regular Contributor
    Join Date
    Aug 2012
    Location
    Rhine Valley
    Posts
    93

    Re: Distinguishing published app from development version

    Quote Originally Posted by theothernt View Post
    There was a post a few months back on the Windows Phone Developer blog which talks about submitting a WP7 and WP8 version of an app and how GUIDs work in that case...

    http://blogs.windows.com/windows_pho...s-phone-8.aspx
    Yes, that was the post I meant. But the blog doesn't talk about the implications on the debug versions on the phone or in the emulator. So I had to check myself if a deployed WP7 app with locally stored data on a WP8 device updates correctly without losing the data. And it does (if you don't scramble the reading routines in the WP8 version...).

    My other point is that copying the WP/ GUID into the WP8 app means that both versions can't be differentiated any more on the test device.

Similar Threads

  1. Replies: 1
    Last Post: 2012-02-15, 01:19
  2. Submit app update which targets subset of devices supported by published version?
    By cip@gmx.at in forum [Archived] Application Submission
    Replies: 1
    Last Post: 2012-02-15, 01:19
  3. wrong version published from ovi
    By florianhaar in forum [Closed] Publishing to Nokia Store
    Replies: 4
    Last Post: 2010-03-15, 07:37
  4. Which Version of Java Development Kit?
    By dm5037 in forum Mobile Java Tools & SDKs
    Replies: 1
    Last Post: 2008-02-08, 22:29
  5. * Scalable UI development on S60 * learning path published
    By jaaura in forum Symbian User Interface
    Replies: 0
    Last Post: 2006-02-28, 11:06

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
×