Talk:Maintaining a WP7 and WP8 version of a same Silverlight application
Hamishwillee - I really like this article
As it says in the subject line, I really like this article. A set of pragmatic no-nonsense approaches that will be useful for a lot of developers.
I've subedited for wiki style - essentially we tend to use bold for "button presses" and "filenames", italic for tools and packages, and Template:Icode for marking up inline code objects. I've also added a chunk of your text into a "Tip". Lastly, I tidied the introduction a little to make it easier to read.
In terms of room for improvement/possible issues:
- Another key thing we're trying to promote is Windows 8 / Windows Phone 8 cross platform stuff. Something to think about (ie solutions for all the platforms).
- The first section "Setting up the projects and sharing code files" explains how to share files, but not exactly why/which files (other than the main.xaml files for styling).
- As a reader my first thought was "Why can't I start with a WP7 project and just graft the interesting bits to get WP8 to run onto my WP7 project file"? As I understand it, the approach adopted here is to use the WP8 project because that has all the settings for building WP8 and then just pull in all the files.
- What files can't you share?
- async/await sounds very cool. Presumably WP8 already has the support and you've just grafted it onto WP7. Do you have to do anything to get this "conditional for WP7 only", since presumably you don't want to depend on the extra package in WP8. Worth clarifying this.
Otherwise looks great.
Thank you for competing!
06:04, 15 November 2012 (EET)
Hamishwillee - Perhaps also worth specifying what sort of application
... since you mean Silverlight/XAML, not XNA.(in the title)
06:09, 15 November 2012 (EET)
Thanks for the remarks. I'll edit the article accordingly in the next few days.
Maintaining a WP7 and WP8 version of a same Silverlight application talks about reflection, another useful option for developers wanting to maintain different versions. Might be worth having a very brief overview of what can be done and then linking to that article.
07:06, 18 December 2012 (EET)
Hamishwillee - PCLWhat do you think about PCL as a tool for maintaining compatibility between WP7 and WP8? See Co-development for Windows Phone 7/8 and Windows 8 guide (or perhaps better http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj720574%28v=vs.105%29.aspx ) for a discussion. I suspect maybe becomes more valuable if you're going to Windows 8 too.
07:35, 18 December 2012 (EET)
Hamishwillee - Thanks Aady
Thank you for merging the content from Adding Windows Phone 8 features to your Windows Phone 7 application by r2d2rigo into this article and redirecting the original article. I agree that this was a worthwhile thing to do and that the merge was fairly effective. In particular its great that you remembered to mention the new section in the introduction as that is something people often forget when merging. I did make a few changes including adding a link to the source in the ArticleMetaData and a note explaining that the content was updated with r2d2rigo's work too - since a lot was put in and this isn't otherwise obvious.
Did you contact r2d2rigo and let him know you were going to do this? As a rule it is good manners to do so if you can? If not, let me know and I will do so.
Probably too much work, but one idea might be to update the example so it now covers all the features of this document. Something to think about.
Thank you again!
04:54, 21 January 2013 (EET)
Aady - ooops I missed to contact r2drigo!!
I have merged 3-4 articles till date from the contest that were closely related and informed all of the respective authors, but for r2drigo. Somehow I missed for this article. Going forward will take more care about it :)
18:08, 21 January 2013 (EET)
Influencer - Like this one very much!
Hey, I like the result of your combined actions to this article! Recently I got the same idea of code sharing via 'Add as link' and I tried it in a sample. Didn't know this artide yet... One thing I discovered in my tests was that one hazard was the namespaces naming convention. So I today wrote one article [How to rename the default namespace in Windows Phone app project]. But I like the idea of an overview of the other ways to shore code, too. That's very convenient and I'm implementing several of the ideas in an update my to app. Thanks.Thomas
talk) 23:03, 5 July 2013 (EEST)(