[Bug]: WPF targeting issue for net6.0-windows

[aurax]

[Bug]: WPF targeting issue for net6.0-windows

[dpvreony]

this is due to dependencies in System.Reactive along with the default targeting of netX-windows being windows 7 which is unsupported

the recommendation is to target net6.0-windows10.0.19041

[aurax]

this is due to dependencies in System.Reactive along with the default targeting of netX-windows being windows 7 which is unsupported

the recommendation is to target net6.0-windows10.0.19041

Strange...
please, check, for example, the "Microsoft.VisualStudio.Threading" NuGet package references. They supports net6.0-windows7.0 target.

<dependencies>
    <group targetFramework=".NETFramework4.7.2">...</group>
    <group targetFramework="net6.0">...</group>
    <group targetFramework="net6.0-windows7.0">...</group>
    <group targetFramework=".NETStandard2.0">...</group>
</dependencies>

[ChrisPulman]

If you were to purely add System.Reactive to a WPF Application with a net8.0-windows TFM you will find yourself with a net462 version of the assembly trying to be added to your project, due to some conflicts this will then lead to incorrect System.Reactive elements being used in your application, ultimately leading to instabilities within your application.
ReactiveUI.WPF has a dependency on System.Reactive and hence we must use their minimum supported windows version in order to have full support for the underlying functions.
We strongly recommend that you follow these guidelines to ensure optimum performance and support. You should always base your minimum on the newest supported windows version within the dependencies included in your application.
Different TFM's have differences in the functionality included, often a newer TFM will be selected to make use of a particular feature.
I hope that you can understand this, many thanks and we hope that you can enjoy using ReactiveUI for your projects.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.