Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial implementation of WinUI with samples and features working #853

Merged
merged 16 commits into from
Jan 11, 2025

Conversation

KasperSK
Copy link
Member

@KasperSK KasperSK commented Apr 6, 2023

This works but navigation is a little rough around the edges, open for input on how it should be done for WinUI

@KasperSK KasperSK requested a review from vb2ae April 6, 2023 06:47
@vb2ae
Copy link
Member

vb2ae commented May 6, 2023

@KasperSK do you want to complete this pr?

@KasperSK
Copy link
Member Author

KasperSK commented May 9, 2023

@KasperSK do you want to complete this pr?

Yes but I think I need to make another commit and fix the small issues. :)

@alex-nicholas
Copy link

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...

@KasperSK
Copy link
Member Author

KasperSK commented Nov 5, 2024

@vb2ae Do you still think we should merge this if I rebase the PR?

@vb2ae
Copy link
Member

vb2ae commented Nov 5, 2024

yes we can fix any bug we find

@vb2ae
Copy link
Member

vb2ae commented Nov 5, 2024

@KasperSK thanks

vb2ae and others added 4 commits December 16, 2024 09:24
Updated README.md to reflect changes in description and package details. Modified `MessageDialogResult.cs` to use `_content` and `_title`. Updated `App.xaml` and `App.xaml.cs` with XML declaration, removed comments, and added navigation to `MenuView`. Updated `Features.WinUI3.csproj` to target .NET 8.0 and adjusted settings. Cleaned up `RootView.xaml.cs` and other files by removing unused directives. Updated `Package.appxmanifest` and `app.manifest` for Windows 10 compatibility. Renamed bindings in `ActionsView.xaml`, `NavigationSourceView.xaml`, and `NavigationTargetView.xaml`. Updated `Microsoft.NET.Test.Sdk` and `Nerdbank.GitVersioning` packages. Improved formatting and consistency in several files. Added strong name key files.
@KasperSK KasperSK requested a review from vb2ae December 18, 2024 08:22
Copy link
Member

@vb2ae vb2ae left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just need to move to .net8.0 from .net6.0 which is no longer supported

@KasperSK
Copy link
Member Author

just need to move to .net8.0 from .net6.0 which is no longer supported

I will get on that :)

This was linked to issues Dec 18, 2024
@vb2ae vb2ae requested a review from Copilot January 11, 2025 15:01
Copy link
Member

@vb2ae vb2ae left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good made the requested change

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 110 out of 125 changed files in this pull request and generated no comments.

Files not reviewed (15)
  • samples/features/Features.Avalonia/Features.Avalonia.csproj: Language not supported
  • samples/features/Features.UWP/Features.UWP.csproj: Language not supported
  • samples/features/Features.WinUI3/App.xaml: Language not supported
  • samples/features/Features.WinUI3/Features.WinUI3.csproj: Language not supported
  • samples/features/Features.WinUI3/MainWindow.xaml: Language not supported
  • samples/features/Features.WinUI3/Package.appxmanifest: Language not supported
  • samples/features/Features.WinUI3/Views/ActionsView.xaml: Language not supported
  • samples/features/Features.WinUI3/Views/Activity/MessageActivityView.xaml: Language not supported
  • samples/features/Features.WinUI3/Views/Activity/PhotoActivityView.xaml: Language not supported
  • samples/features/Features.WinUI3/Views/BindingsView.xaml: Language not supported
  • README.md: Evaluated as low risk
  • samples/features/Features.CrossPlatform.Shared/Results/VisualStateResult.cs: Evaluated as low risk
  • .github/workflows/dotnet.yml: Evaluated as low risk
  • samples/features/Features.CrossPlatform.Shared/Results/MessageDialogResult.cs: Evaluated as low risk
  • samples/features/Features.WinUI3/Views/Activity/PhotoActivityView.xaml.cs: Evaluated as low risk
Comments suppressed due to low confidence (1)

samples/features/Features.WinUI3/MainWindow.xaml.cs:31

  • [nitpick] The variable name myButton is ambiguous. It should be renamed to submitButton.
private void myButton_Click(object sender, RoutedEventArgs e)
@KasperSK
Copy link
Member Author

Thanks Ken, I have not had any time over the holidays. I will merge this and then we should work with WinUI 3 :)

@KasperSK KasperSK merged commit d644b15 into master Jan 11, 2025
4 checks passed
@vb2ae vb2ae deleted the feature/WinUI branch January 11, 2025 15:59
@vb2ae
Copy link
Member

vb2ae commented Jan 11, 2025

@KasperSK no problem. Hope you enjoyed the holidays

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

RFC: Do somebody work on WinUI 3 support? WinUI 3 support
3 participants