![]() 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |