WPF support on .NET Core 3.0 breaks .NET Core 3.0 consumers on Linux/Mac #35
Comments
AArnott
added a commit
to AArnott/vs-threading
that referenced
this issue
Nov 5, 2019
Works around dotnet/sdk#3592 as described in AArnott/Xunit.StaFact#35
2 tasks
AArnott
added a commit
that referenced
this issue
Dec 11, 2019
.NET Core 3.0's design for WPF/WinForms requires that a NuGet package that supports WPF/WinForms on .NET Core 3.0 can only be installed to a Windows-targeted project and cannot be restored or built on another operating system. Since we both want to support WPF/WinForms on .NET Core 3.0 as well as continue to support Xunit.StaFact being used on non-Windows operating systems, we have to split the package in two. Fixes #35
AArnott
added a commit
that referenced
this issue
May 3, 2020
AArnott
added a commit
that referenced
this issue
May 3, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The mere presence of WPF support on .NET Core 3.0 for this package injects artifacts into the package nuspec file that breaks the build for anyone depending on this package and building on mac/linux and targeting .NET Core 3.0. Even though they don't care about WPF, the dependency breaks the build.
See dotnet/sdk#3592
We'll need to break up WPF support on .NET Core 3.0 into its own package, evidently. :(
The text was updated successfully, but these errors were encountered: