Separate NuGet packages for different UI frameworks?

[ekdahl]

If I have a WPF application targeting e.g. net6.0-windows10.0.18362.0, the WinUI library is referenced instead of the WPF library (that should be referenced). How can this be solved? Now, I need to remove the NuGet package and directly reference the DLL instead.

A few thoughts:

• Separate NuGet packages depending of what framework is used (WPF/WinUI/UWP)
• Can UseWPF/UseWinUI element in project file be used?

BR, Fredrik

[ClemensFischer]

How is a WPF app targeting net6.0-windows10.0.18362.0? There should be

<OutputType>WinExe</OutputType>
<TargetFramework>net6.0-windows</TargetFramework>
<UseWPF>true</UseWPF>

in the project file. I can't reproduce the issue.

[ekdahl]

Because this is not the only NuGet package used in my application. My application also uses this package, that needs net6.0-windows10.0.18362.0 (probably related to CsWinRT).

Source of project file here: https://github.com/iNKORE-NET/UI.WPF.Modern/blob/main/source/iNKORE.UI.WPF.Modern/iNKORE.UI.WPF.Modern.csproj

[ClemensFischer]

I have created another NuGet package XAML.MapControl.WPF that contains only the WPF versions.

[ekdahl]

Thanks a lot, very appreciated!

[ClemensFischer]

The same problem occured to another user with the MapProjections library. I am now going to follow your suggestion to provide only platform-specific NuGet packages.

I will keep the original package IDs without .WPF suffix for the packages that target WPF, and hence drop the XAML.MapControl.WPF package with the next release.

[ClemensFischer]

Or better, I will drop the original packages and keep only the one(s) with the .WPF suffix

[OWiger]

Or better, I will drop the original packages and keep only the one(s) with the .WPF suffix

This fixed my issue, thanks! :)