X3 REUNION SWITCH TARGET UPGRADE
X3 REUNION SWITCH TARGET WINDOWS

As we noted earlier, the UI project needs to be multi-targeted to generate builds for both UWP and WinUI. I’ll refactor this style into a ResourceDictionary called StyleResources, which I’ll also add to the UI project.īecause the UI project was created as a WinUI Desktop class library, it only has a single target framework defined, being net5.0-windows2.0. I also have an implicit Button style that I used to center the buttons on both pages, which was defined in the Application.Resources in App.xaml. The first thing we’re going to do is to move both MainPage and SecondPage (both XAML and XAML.cs files) to the UI project.

The UI library is where all the pages and other XAML resources are going to reside, allowing us to multi-target both UWP (i.e. We need to make sure that both the UWP and the WinUI Desktop projects have a reference to the UI multi-targeted library. the WinUI Desktop target – set the (Package) project to be the startup project to debug the WinUI Desktop target). the UWP target) and a WinUI with Package project (i.e.

X3 REUNION SWITCH TARGET WINDOWS

The solution structure should now look like this – you can see that there’s a Universal Windows project (i.e. We’ll go ahead and add both the WinUI Desktop project (Blank App, Packaged (WinUI in Desktop) project template)Īnd the multi-targeted library (use the Class Library (WinUI in Desktop) project template) to the solution. The SecondPage has a single button that triggers navigation back to MainPage. The MainPage has a single button that triggers navigation to the SecondPage. As you can see it’s a simple application that has two pages, MainPage and SecondPage. Starting with the UWP application we’re going to migrate. This will allow us to pick either, or both, projects for debugging. In order to do this, we’re going to take an existing UWP application, move all the UI elements (pages, resources etc) into a separate multi-targeted library and then add a WinUI Desktop (and packaging) project. With this in mind, let’s work on the assumption that we need to be able to build and run either, or both, the UWP app and the WinUI app. In fact, you’ll probably want to run your UWP application in parallel with the new WinUI application whilst you check stability, features, performance etc. Given we’re still a way out from WinUI being released, it’s likely that you’ll have to run this migration process multiple times. find and replace the Windows.UI.Xaml namespaces with Microsoft.UI.Xaml namespaces).

Well, this clearly isn’t going to be the case since WinUI3.0 for Desktop is missing some core pieces of the UWP app model, such as application lifecycle, so those things won’t easily migrate.Įven if we ignore the features that won’t migrate currently, the proposed approach is a one way migration (eg. One of the features of WinUI that has been touted is that switching from UWP to WinUI is going to be as simple as switching out some namespaces. The rest of this post will be focused on migrating a UWP application to WinUI3.0 for Desktop. This is what you should be planning on supporting as you look to migrate your UWP application to WinUI3.0. What’s more likely at this stage is for Project Reunion to light up some, if not all, the key UWP features inside of a. DO NOT hold out for this!Īs you can see from the published roadmap WinUI3 in UWP is pushing into the. Support for WinUI3.0 in UWP has slipped from a scheduled release into the wish list bucket (see published roadmap). For those who are waiting for WinUI3.0 in UWP to ship, you’re going to be sorely disappointed. WinUI Desktop v UWPīefore we get on and look at the migration process, I’m going to point a big bright red flag at the elephant in the room. In this post we’ll look at a migration approach that will allow you to keep your UWP app running in parallel to a WinUI 3.0 desktop app.

X3 REUNION SWITCH TARGET UPGRADE

As we get close to preview 4 of WinUI 3.0 (it’s Feb 2021 already so where’s my WinUI preview4!), now’s the time to start looking at how you’re going to upgrade your UWP application to WinUI3.0.

X3 reunion switch target