Linked by Thom Holwerda on Fri 1st Feb 2013 18:25 UTC
Windows A few days ago, Microsoft released the long-awaited Windows Phone 7.8 update for all those users who will be stuck on Windows Phone 7 forever because there's no upgrade path to Windows Phone 8 other than buying a new phone. Now that it's here, what, exactly, does WP7.8 to the table?
Thread beginning with comment 551369
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[8]: Comment by Nelson
by Nelson on Mon 4th Feb 2013 18:27 UTC in reply to "RE[7]: Comment by Nelson"
Nelson
Member since:
2005-11-29


"Android applications are generally forward-compatible with new versions of the Android platform."


This exact thing happens with Windows Phone. The Windows Phone 7 environment is loaded for Windows Phone 8 apps.

This also happens on Windows 8 when providing compatibility for the (limited) number of Store Apps that were built using the Release Candidate SDK.


It is only true for Windows Phone where you need to port WP7 apps. http://news.softpedia.com/news/Port-Windows-Phone-Apps-to-Windows-8...


Windows Phone apps will never run on Windows 8 unmodified. Ever. That's a conscious design choice. Microsoft chose to shrink their Desktop OS down rather than blow their Phone OS up for tablet sizes.

The question we're talking about here is feasibility, which is what I've mentioned in my original comment.


"A Windows Store app using C++, C#, or Visual Basic, using XAML, is the preferred model for ports from Windows Phone 7. If you are familiar with Silverlight, you can port to a Windows Store app using XAML by using familiar languages like C# or Visual Basic, and a similar set of UI elements and APIs"

Similar != same. Another:


You're never going to get the same exact code to run unmodified on Windows 8. That's never going to happen. Phone experiences are much different.

The areas of strength and scenarios to enable are ones where developers can re use a great amount of code across platforms. This is already the case.

Silverlight and Windows 8's XAML stack are so similar they are practically twins. A few namespaces changed, some functionality is missing in one, or new to another. By and large porting from Windows Phone to Windows 8 isn't hard.

What I'm complaining about are common sense things they have not done to both make this easier, and enhance the development experience on the phone as a whole.


Now we have WP7 apps, WP8 apps, Win8 apps, RT apps and end of this year Windows 9 Blue appears which is going to change that story once more.


And again, you trot out this lie. I've already explained that Windows Phone 7 and Windows Phone 8 apps are the same environment with new APIs. Much like Mango (Windows Phone 7.5) was to Windows Phone 7.0.

The differences are often very minute and most WP7 apps porting to WP8 are a recompile, with no code changes away.

Windows 8 and Windows RT apps are the same app: A Windows Store app. In fact, in an article by Microsoft you quote, they explain this.

Also, there is no information on Windows Blue, but there's no reason to believe it will use a completely different runtime environment other than WinRT.

Windows 8 already operates under two environments. RTM and RC environments for apps. You can look at Microsoft's code by reflecting the .NET assemblies and see that they do the logic swapping at runtime.

This is similar to how Silverlight kept versions of SL2.0 and 3.0 inside the 4.0 runtime.


Again! Horrible fragmentation, deprecation and new API turnaround every year.


You do not know what you're talking about.

Reply Parent Score: 3