No error when Microsoft.NET.Sdk + net5.0 (without net5.0-windows)
See original GitHub issue<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<OutputType>WinExe</OutputType>
<TargetFramework>net5.0</TargetFramework>
<UseWindowsForms>true</UseWindowsForms>
</PropertyGroup>
</Project>
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
NET SDK error list - .NET CLI
A complete list of NETSDKxxxx errors, with links to more info where more info is available.
Read more >When TargetFramework=net5.0-windows, dotnet pack ...
NET Framework, which is how SDKs older than 5.0.100 would interpret it. I am not sure. Does the MSBuild log show the SDK...
Read more >Visual Studio Build Tools fails to recognize "net5.0-windows"
1 Answer 1 ... If you want to use Build Tool, you should note that .NET 5.0 is released since 16.8 . So...
Read more >Unable to reference project in test project: net5.0-windows / ...
I create a new project UnitTestingPractice in a new solution and target .NET 5.0. I then create a test project--either xUnit or Unit...
Read more >Test Explorer fails to execute any tests under netcore3.1 ...
I have a unit test project that is multi-targeted (net461;netcoreapp3.1;net5.0-windows). This project references Microsoft.NET.Test.Sdk version 16.5.0 for ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh I just got a binlog and I know what’s going on. It’s not erroring here because the TargetPlatformIdentifier is set to Windows because the target platform workaround is still in RC1. I just merged the change to remove the workaround so this should error in RC2: https://github.com/dotnet/sdk/pull/13168
So it is fixed in RC2. Closing