Please note that as of October 24, 2014, the Nokia Developer Wiki will no longer be accepting user contributions, including new entries, edits and comments, as we begin transitioning to our new home, in the Windows Phone Development Wiki. We plan to move over the majority of the existing entries. Thanks for all your past and future contributions.
Talk:Application update prompt using Cimbalino Windows Phone Toolkit
Hamishwillee - Review
Interestingly, we also have Checking for updates from inside a Windows Phone app which explains the inner working of MarketplaceInformationService - and indeed the author updated Cimbalino with the code. However that article only covers the process from "first principles" and introduces Cimbalino/MarketplaceInformationService - it doesn't actually show how to use it. So from my perspective this is a very useful article.
What I'd like to do is propose a name change to differentiate the articles, and cross link them. How about "App update notification using Cimbalino Windows Phone Toolkit"? I'd then update this to explain the other article, and in the other article explain the how to.
I would also like to change the licencing of the uploaded file from Nokia standard T&Cs to very permissive MIT licence. Are you OK with that?
talk) 06:08, 29 October 2013 (EET)(
I Jones - RE:Hamishwillee - Review
Hi HamishThat all sounds good to me. What do you need me to do?
talk) 11:00, 29 October 2013 (EET)(
Hamishwillee - think about "reprompting"
I've renamed the page, and I'll do the other suggestions over the coming days.
One thing you could do is consider where this code should be executed. If you run it every time the app is run then the user may update, but they may find it annoying and just remove the app or stop using it. This would be disappointing if the reason they stopped is just because their internet connection is unreliable (and perhaps only temporarily). Could you perhaps add code to show how to do this prompting after every 5 uses (say) until they've updated.
For bonus points ... wrap this up in a library making the refresh notification rate configurable and also making it easy for others to translate the strings. If you go this far, I'd suggest hosting it on github.
talk) 08:06, 30 October 2013 (EET)(
Hamishwillee - ... and even disable the appIt might also be worth saying a few words /options about what to do if they won't update the app. I don't know what the store says, but perhaps it would be OK to actually block continuing the app.
talk) 08:10, 30 October 2013 (EET)(
I Jones - RE:Hamishwillee - ReviewI've updated the article with your suggestions, the whole process is now integrated into a class. I'm having issues with updating the source code zip file examples though.
talk) 13:56, 31 October 2013 (EET)(
Hamishwillee - Thanks.
Hi Thanks! I hope to review this again very shortly and provide more feedback if needed. In the meantime, I've sent you my email address in a private message - so you can email me the zip and I'll see if I can upload.
talk) 05:32, 1 November 2013 (EET)(
Saramgsilva - Same article
Pedro Lamas wrote this article
talk) 20:16, 2 November 2013 (EET)(
Hamishwillee - Sara, yes we know
True, and I made the point in my review up the top.
In an ideal world we would merge, however this article is much more simple than Pedro's, and in my opinion merging would actually be less useful for developers because "understanding how it works" is not actually necessary to using it ... and makes the story more complicated. On the other hand, I don't want to cut back Pedro's interesting article to make it more functional. So as a compromise I'm cross linking them (in progress)
Iestyn, please email me the file to upload
talk) 09:01, 4 November 2013 (EET)(
Hamishwillee - Subedited/Reviewed
Firstly thanks for your updates. Make sense to me and address my concern - much appreciated.
I gave it a further subedit to improve the introduction and add cross links to the other article. I also added a little more explanation in some of the sections. Can you please check that you're still OK with it.
All then that is missing is the code example file.
talk) 09:23, 4 November 2013 (EET)(
I tested the code, also run the sample code.
I was publishing the App with this update, but just before click submit I had a doubt and did the last test, turn off all internet connections.
Well I did good as the App crash! I used also a try catch, but nothing.
Is it a known issue? Do I'm wronging something ? Anyway worth to deepen that as if I published the App in that way it would be no good at all, so worth to know how to manage that.
Can you tell more info about that?
More is not clear if to align the product ID to Dev Portal must be done just to test the App then restore the old product ID or can be published with the new product ID.
This is very important to know, as changing the product ID, you are not able to install the new app over the old. You must delete it then install again with the new product ID. This could be frustrating in "developer mode" but not a problem if you know the behavior. But what happens when published ? Does user have to uninstall the app after this update?
This is another aspect to clarify very good. In that moment I don't feel to risk to update my App until all aspect are not clear. As the solution is very interesting, can you please provide more information and tell your experience with published App?
talk) 00:05, 18 December 2013 (EET)(
I Jones - RE:Galazzo -
Thanks for your interest in the article. I've added a few extra comments on AppID and internet connections. Please take a look and let me know what you think.
As for my experience with a published app, it's working well in apps I've deployed. The users don't need to uninstall and re install as this taken care of by the marketplace.I also have code in my App.Xaml.cs to check for Internet Connectivity before any connection. It uses the NetworkInformation.GetIsNetworkAvailable() method to set a private variable and update when a change event is raised. This saves checking the device status every time and improves performance.
talk) 15:43, 7 January 2014 (EET)(
Hamishwillee - Should the network check be in the component?
Thanks for the update - lets see what Sebastiano says.
BTW, would it make sense to run the network check within the component - one less thing for users to remember when trying this code?
talk) 01:31, 8 January 2014 (EET)(
Lipskii - Little Problem
Hi everyone ! I'm completely beginner in writing apps, I'm doing step after step, just like this article says and I have an error...
"The name 'AppSettings' does not exist in the current context"
E:\Documents\Visual Studio 2012\Projects\App1 local, update\App1\ApplicationUpdateReminder.cs 46 32 App1I don't know how to fix it, help, please.
talk) 01:34, 21 April 2014 (EEST)(
I Jones - RE:Lipskii - Little Problem
HiAppSettings is a helper class I wrote to help store/read settings in IsolatedStorage. If you check the downloads for this article, the .zip file should contain the class. If you're still struggling, I can always send you the file :)
talk) 01:42, 21 April 2014 (EEST)(
Lipskii - RE:I Jones - RE:Lipskii - Little Problem
Unfortunately i haven't found it yet, that would be awesome if you could upload it somewhere :)thanks a lot !
talk) 14:50, 21 April 2014 (EEST)(
Umashankarpathak - unable to get app info from marketplace
Hi, Thanks for article but I am getting System.Net.WebException at await _informationService.GetAppInformationAsync().Please help me to fix it.
talk) 08:08, 9 October 2014 (UTC)(