Closed GeertvanHorrik closed 5 years ago
Without using netcoreapp3.0, the packages are created correctly, so I am assuming the migration of step 1 have been completed successfully.
For WPF, you don't need the extras at all anymore. The recommended approach would be to use the new Microsoft.NET.Sdk.WindowsDesktop
SDK.
The extras will likely be relevant for Xamarin and UWP.
Thanks for your reply. The advantage of extras is that we can use them for all our projects (WPF apps, web apps, libs (WPF, UWP and netstandard all combined). Whenever we use WindowsDesktop, we can't really multitarget (right?).
So we would like to keep using extras since it has brought us benefit and will give us benefit if we need to be flexible in the future (we've standardized our project structure).
The end goal is to allow the extras to co-exist, but the WPF-related functionality will call in the desktop one where available. Just hasn't been updated to co-exist yet.
Not sure I understand your reply, is there anything I can do to make this work (pr, update my stuff, whatever you think is actionable from my side)?
Done in #133
We are using this (happily!) for all our projects, and want to investigate whether we can add support for .NET Core 3.0 for WPF in all our libraries.
I am now getting this error:
I am coming from 1.5.4, so made 2 changes:
1) Update to
Project Sdk="MSBuild.Sdk.Extras"
instead of referencing it as package reference 2) Add netcoreapp3.0 as target frameworkWill keep posting investigations here, it might be of use for others.