-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added net6.0-windows on WPF and WinForms and workaround MSBuild.Sdk.Extras issue #260
Added net6.0-windows on WPF and WinForms and workaround MSBuild.Sdk.Extras issue #260
Conversation
multi targeting new and legacy TFMs is not supported on mac, so we don't build net6 TFMs on mac and with our samples having project references, this fails the samples build.
this adds a build check for CI
In my opinion the netcore sample (which should be renamed to desktop?) is a good test to multi target these 3 TFMs in an app project, so we should keep my last commit (which is failing the build). As for the build error:
I repro that build error locally, it's a weird one I've seen before sometimes happening. Now we repro consistently. Replacing Additionally, we should try to replace all the samples csproj still using the old-style SDK and see if we could use the new style, as well as multi target new and legacy TFMs if possible (i.e. the android sample would target both This would help prevent what just happened with the 3.6.2/3.6.3 releases (I take full responsibility). |
Is there any namespace somewhere that's named MediaPlayer and that conflicts with the type ? Do you have more info on this ? why did that not break before ? (different SDK ?) |
SDK issue I'd say. Removing the macos target fixes it (though the build error does not prevent the DLL to be built). Specific to mac/ios toolchain/SDK https://code.videolan.org/videolan/LibVLCSharp/-/issues/326 - <TargetFrameworks Condition="$([MSBuild]::IsOsPlatform('Windows'))">net6.0;net6.0-windows;net6.0-macos</TargetFrameworks>
+ <TargetFrameworks Condition="$([MSBuild]::IsOsPlatform('Windows'))">net6.0;net6.0-windows</TargetFrameworks> |
For WinForms and WPF samples, this change is required for net6.0 (breaks legacy TFMs) - <Project Sdk="Microsoft.NET.Sdk.WindowsDesktop">
+ <Project Sdk="Microsoft.NET.Sdk"> Cross-targetting for our "internal" samples project seems like a lot of overhead now. Maybe we should just keep net6.0 / latest for these test samples? |
Thanks! |
Description of Change
DESKTOP
constant to replace the (flaky)NETFRAMEWORK || NETSTANDARD || NET6_0
Issues Resolved
Users referencing LVS.WinForms in .net6.0 should have a working project now
API Changes
None (Fixes missing APIs in 3.6.3)
Platforms Affected
Behavioral/Visual Changes
None
Before/After Screenshots
Not applicable
Testing Procedure
PR Checklist