![]() If you choose the Universal device family, and your app calls APIs that are implemented only in the Desktop device family, then you can guard those calls with adaptive code. Port the project to an app targeting the Universal or the Desktop device family. Or, you can create different solutions and still share the same items using links. You can create a solution with a Shared project, and continue to share source code, markup files, and other assets and resources between the two projects. Port the contents of the Windows project to an app targeting the Universal or the Desktop device family and also port the contents of the WindowsPhone project to an app targeting the Universal or the Mobile device family.If applicable, salvage any other content from the WindowsPhone project, using it either unconditionally or adaptively. Port the contents of the Windows project to an app targeting the Universal device family.If applicable, salvage any other content from the Windows project, using it either unconditionally or adaptively. Port the contents of the WindowsPhone project to an app targeting the Universal device family.If applicable, salvage any other content from the Windows and WindowsPhone projects, and use that content either unconditionally in the app or conditional on the device that your app happens to be running on at the time (the latter behavior is known as adaptive). Port the contents of the Shared project to an app targeting the Universal device family.The nature of the Universal 8.1 app will determine which of these options is best for your case. With an app like that, you can choose to port it to a single app that targets the Universal device family (in which case you will want the app to adapt itself to different devices), or you can choose to port it as more than one app, perhaps one targeting the Desktop device family and another targeting the Mobile device family. Or they contain the same features but they implement those features using different techniques or different technology. Other times, the Windows 8.1 and/or the Windows Phone 8.1 form of the app contain unique features. You'll essentially port the contents of the Shared project and you'll need to use little or nothing from the other two projects because there'll be little or nothing in them. An app like that is an ideal candidate for porting to a single Windows 10 app that targets the Universal device family (and that you can install onto the widest range of devices). Often, an 8.1 Universal Windows app offers the same features-and does so using the same code and markup-in both its Windows 8.1 and Windows Phone 8.1 forms. This is the project that contains source code, markup files, and other assets and resources that are used by both of the other two projects. This is the project that builds the app package for Windows Phone 8.1. This is the project that builds the app package for Windows 8.1. ![]() Let's say the project's name is AppName_81. If you have a Universal 8.1 appĪ Universal 8.1 app is built from an 8.1 Universal App project. ![]() That's explained in the following sections. Your first steps in planning exactly what to do with your current app or apps will depend on the kinds of apps and projects you have. Just as before, you can still choose between C++, C#, and Visual Basic for the programming language to use along with the XAML UI framework. While porting, you'll find that Windows 10 shares the majority of APIs with the previous platforms, as well as XAML markup, UI framework, and tooling, and you'll find it all reassuringly familiar. ![]() For more background on Windows 10, UWP apps, and the concepts of adaptive code and adaptive UI that we'll mention in this porting guide, see Guide to UWP apps. With Windows 10, you can create a Universal Windows Platform (UWP) app, which is a single app package that your customers can install onto every kind of device. If you have a Universal 8.1 app-whether it's targeting Windows 8.1, Windows Phone 8.1, or both-then you'll find that your source code and skills will port smoothly to Windows 10. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |