Windows Phone 8.1 Development Technology Overview (Universal APP)

A moment ago really lazy WP8.1 has come out so long time now just update blog Let everyone wait, today I first introduce WP 8.1 development framework, what is Microsoft's respected Universal APP, and we want to develop Universal What to look for when you're in the app.

If you are a just contact with WP development friends can first look at my previous article to understand the story background: Windows Phone 8 and Windows 8 Development Technology Overview

Let's start by perfecting a concept-that's the difference between Windows Phone 8.1 and Windows Phone 8.0

1. The WP8.0 development architecture is based on the Silverlight runtime runtime

2. WP 8.1 Development architecture has two Silverlight Runtime/windwos Xmal (equivalent to Windows 8.1) runtime

The Universal APP I'm talking about in the future is based on the Windows XAML runtime, and the new feature that I'll cover later in detail WP8.1 will also be based on the content of the Windows Xmal framework.

Above this picture is our latest Windows & Windows Phone 8.1 Development Platform Architecture diagram Here we can see very clearly that the blue part is universal including WinJS, C #, VB, C + + only Silverligh T is unique to Windows Phone, so if we want to develop a Universal APP that can be extended to WP 8.1 based on a Windows 8.0/8.1 development architecture, this process is very handy.

In addition, I also introduced to you how to share code in WP8.0, in the 8.1 universal app we can share more code and very convenient, this common content promotion is a considerable leap ( from 8.0 share 27% to 8.1 share 77% so we can share code in the process of development, and can use Universal's application template for code sharing in VS2013.

And then I'll introduce you to the Windows Store Universal APP in the VS2013 Upgrade Update 2 installation WP 8.1 development environment, we will see Universal Apps templates ( also in Winis and C + + With Universal templates )

Here is the project structure of the Universal app, which automatically creates the application project for WIN8.1 and WP8.1 in a sln and a shared project, and the WP8.0 development student must have noticed this shared project With a App.xaml and App.xaml.cs file This means that thelife cycle of WP is consistent with Win 8.1 , and the small partners do not have to deal with tombstones. (There is a tombstone in the Silverlight schema), and our files in share project are automatically shared to Win8.1 and WP8.1, and in WP8.1 and win 8.1, there are defined platforms that are unique to the content.

And the Universal APP also supports Windows Runtime components

In addition, under the Windows XAML framework we can provide a lot of universal for the underlying controls, in other words, the same controls run on different platforms , such as: Hub, appbar/commandbar,date/ Time pickers and List pickers,listview,multi-select; containers, swipe selection,flyouts,media.

Of course there are exactly the same , can be more easily share code.

There must be a friend here who wants to ask me what to do with the 8.0 Silverlight app I've developed? Could you upgrade to 8.1? The answer, of course, is yes! can be upgraded to 8.1, but there are some issues to be aware of, I also here to introduce you.

First of all in WP Silverlight 8.1 we can upgrade directly from the 8.0 application, very convenient, here is to note that there are some features currently only available in the Silverlight framework can be used, in Windows Xaml temporarily not:

That is, if your app uses a feature in 8.0 and you want to continue using it in 8.1, you must use the Silverlight framework.

Upgrade considerations-Breaking Changes

But here I have a special note: if your WP Silverlight 8.0 app upgrade to 8.1 uses two features then you need to consider the Update method.

Background Audio is not supported in 8.1 and requires you to write Background task from

Continuous background Execution agent is no longer supported, It is also necessary to use the background task instead

For implementation, refer to Windows 8.1 app development Background Tasks overview (Windows XAML)

So we have several options when choosing to upgrade or develop a new WP8.1 application.

1. If we just want to be a WP 8.1 app then any development framework is appropriate.

2. If we already have a Windows Store app, then we choose Windows Xaml Framework Development to maximize the reuse of existing code.

3. If our app uses lock screen, lense, or VoIP, then we can only choose WP Silverlight's development framework.

4. If it is a music app and you want to use background playback then you can only use the 8.0 WP Silverlight Framework or WP 8.1 Windows XAML framework.

5. If it is an existing WP Silverlight project we can choose to upgrade to Silverlight 8.1 or refactor to WP 8.1 Windows XAML framework.

Today I give everyone to take so much content, the back I will continue to introduce WP8.1 new feature please everyone look forward to!

Welcome everyone to communicate with me here or on Sina Weibo @ Wang Bo _nick