Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add `.net6` target framework
See original GitHub issueCurrently it’s not possible to move UI into a separate project (that targets just .net6) due to MauiToolkint not targeting that framework. In XCT it was possible. Microsoft.Maui.Dependencies has .net6, so it’s also possible in vanilla Maui.
Could you please add .net6 and another target framework to Maui toolkit (and Xamarin.CommunityToolkit.MauiCompat)?
Workardond:
Replace .net6 with net6.0-android30 (and all other frameworks that your app builds for) in all of app’s projects.
Downsides: increases build time, and enables platform specific code in project where there shouldn’t be any.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@brminnick Thanks for approving the PR! Could you please make the same change for
Xamarin.CommunityToolkit.MauiCompat?the above solution is’nt working for my solution I am adding blazor web assembly reference to .NET Maui Blazor project i have added this
<UseMaui>true</UseMaui>and added target frameworks for all builds in the Blazor Wasm project , please help with a workaround