New Fluent Navigation projects have several issues #361
Labels
bug
Something isn't working
locked-due-to-inactivity
MVVM_DI
Issues related to MVVM and Dependency Injection.
Describe the bug
New projects will not build with (as of writing) the latest VS 2022 (
17.3.1
)/dotnet6.0.400
build. This seems to be largely due to a regression in dotnet 6.dotnet/wpf#6792
There is a workaround outlined here.
dotnet/wpf#6792 (comment)
I see you're already aware of this issue though.
#289
There is one more issue.
Microsoft.Toolkit.Mvvm
is deprecated in favor ofCommunityToolkit.Mvvm
. Switching out the packages has some reference issues that are easy to clean up. However,ICommand
is no longer available. Doing a nuget search to see where else this could live, I can only find references to theMicrosoft.Toolkit.Mvvm
package. This will require either a backfill or looking for an alternate solution. I just started using wpfui today so I'm not terribly confident in issuing a PR with either approach. Interestingly, if you install both packages and repoint everything except for ICommand to the new community toolkit the app seems to work fine, but that's an ugly bandaid.To Reproduce
Steps to reproduce the behavior:
0. Make sure VS version
17.3.1
and dotnet6.0.400
are installed.Create a new project
flow to create aWPF UI - Fluent Navigation
project.Expected behavior
New projects should build/run out of the box.
Desktop (please complete the following information):
Version 10.0.22000 Build 22000
(Windows 11)Additional context
VS info dump
The text was updated successfully, but these errors were encountered: