Initial implementation of WinUI with samples and features working #853
Conversation
There was a problem hiding this comment.
You are right! Default files 😅 What do you think about the way navigation is done in the Features project? I am unsure if we should change displayrootview to not set a frame as per default since the navigation UI needs to be user supplied.
There was a problem hiding this comment.
To answer your question yes the user should supply the frame.
Does this work with desktop, uap or both?
There was a problem hiding this comment.
In UAP the bootstrapper creates the frame. How ever there is an overwrite that enables the user to create the frame themselves. But since the UI in UAP is setup to have the back button in the window chrome it is not an issue.
I focused on WinUI in desktop since reading about the subject that was the direction things where going and UAP was on the way out.
|
@KasperSK do you want to complete this pr? |
Yes but I think I need to make another commit and fix the small issues. :) |
|
Just wondering how far off we are from seeing this in a release? I've been using caliburn.micro in WPF apps for nearly 8 years, but I'm currently working on a WinUI app, and the amount of non-sense you have to do for basic View/ViewModel binding (and the amount of concrete references you need to have from the view to the view model) is just staggering after working in a fully auto-wired caliburn app... |
This works but navigation is a little rough around the edges, open for input on how it should be done for WinUI