Does not work when TargetFramework is net5.0-windows
See original GitHub issueRunnin dotnet-outdated against the following project generates no updates:
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net5.0-windows</TargetFramework>
<OutputType>Exe</OutputType>
</PropertyGroup>
<ItemGroup>
<PackageReference Include="Newtonsoft.Json" Version="12.0.2" />
</ItemGroup>
</Project>
Changing the TargetFramework
to simply net5.0
causes an update to be found.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
When TargetFramework=net5.0-windows, dotnet pack ...
I got it resolved by just changing the .net5.0 to .net5.0-windows as well.
Read more >Target frameworks in SDK-style projects - .NET
A target framework is typically referenced by a TFM. The following table shows the target frameworks supported by the .NET SDK and the...
Read more >net5.0" and "net.5.0-windows7.0" aren't compatible [closed]
My server is. Net5.0, the project DLL that I want to reference is. Net5.0-windows, the reference display is not compatible,. Net5.0 cannot ...
Read more >Experimenting with .NET 5 Target Framework Names and the ...
If we change the TFM to .net5.0-windows, this is what we see when we build the project (I'm just going to show the...
Read more >How to Prepare for .NET 5 End-of-Support on May 8
Open the project file (the .csproj, .vbproj or *.fsproj file). · Change the target framework value from net5.0 to net6.0. The target framework...
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
I just tried the example provided and it detects an update. Also running with -u option updates the package correctly.
Cannot seem to reproduce the issue
No news, but if anyone wants to dig into the details and create a pull request it would be most welcome.