At the very least you'll need to recompile as the 2 platforms will require targetting different versions of the. Update: Microsoft have provided some early stage guidance on making such a port. It includes some namespace and API mappings. Looking at the APIs, and ignoring differences in user experience, I'd say: not difficult but not trivial.
In that case you either have to decide to completely rewrite the application or try out an XNA replacement such as MonoGame.
Following these directives you could have a very platform specific user experience, yet a very unified code base. I hope this adds valuable information for you in addition to the great answers you already got from the other guys. How are we doing? Please help us improve Stack Overflow. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Collectives on Stack Overflow. Learn more. How easy is it to port a Windows Phone 7 application to Metro on a Windows 8 tablet? Ask Question. Asked 10 years, 4 months ago. In this case, the app can be installed onto the widest range of devices. If your app calls APIs that are implemented only in the mobile device family, then you can guard those calls with adaptive code. Alternatively, you can choose to port your app to an app that targets the mobile device family in which case you don't need to write adaptive code.
The option you choose from the previous section will determine the range of devices that your app or apps will run on, and that may well be a very wide range of devices. Even limiting your app to the mobile device family still leaves you with a wide range of screen sizes to support. So, since your app will be running on form factors that it didn't formerly support, test your UI on those form factors and make any change necessary so that your UI adapts appropriately on each.
You can think of this is a post-porting task, or a porting stretch-goal, and there is an example of it in practice in the Bookstore2 case study. Before or during the porting, consider whether your app could be improved by refactoring it so that code with a similar purpose is gathered together in layers and not scattered arbitrarily. Factoring your UWP app into layers like those described above makes it easier for you to make your app correct, to test it, and then subsequently to read and maintain it.
This pattern keeps the data, business, and UI parts of your app separate from one another. Even within the UI it can keep state and behavior separate, and separately testable, from the visuals.
It's likely that you'll be able to re-use much of the view model and view parts across devices, too. As you read this porting guide, you can refer to Namespace and class mappings. Fairly straightforward mapping is the general rule, and the namespace and class mappings table describes any exceptions. At the feature level, the good news is that there's very little that's not supported in the UWP.
Most of your skill set and source code translates very well over to UWP apps, as you'll read in the rest of this porting guide. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
Contents Exit focus mode. More Decks by Michele Capra. See All by Michele Capra. Other Decks in Technology. See All in Technology. Unsolicited bulk mail or bulk advertising. Any link to or advocacy of virus, spyware, malware, or phishing sites. Any other inappropriate content or behavior as defined by the Terms of Use or Code of Conduct. Any image, link, or discussion related to child pornography, child nudity, or other child abuse or exploitation.
Details required : characters remaining Cancel Submit 6 people found this reply helpful. Was this reply helpful?
0コメント