Add a way to disable .NET Core 2.1 warning
See original GitHub issueOur builds are full of warnings:
.NET Core 2.1 is no longer supported and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the .NET support policy.
We are sure, that our libraries are should be compiled and run under netstandard2.0
.
<NoWarn>NETSDK1138</NoWarn>
disables this warning during the build, but how to disable it during setup-dotnet
?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Suppress code analysis warnings - .NET - Microsoft Learn
This article covers the various ways you can suppress warnings from code ... You can disable a rule that's causing a warning by...
Read more >How to disable precompiled views in net core 2.1+ / net 5 for ...
Just reference Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation in your .csproj file conditionally. Don't forget to adjust the version, you ...
Read more >Suppressing the startup and shutdown messages in ASP.NET ...
In this post, I show how you can disable the startup message shown in the console when you run an ASP.NET Core application....
Read more >Fix for "missing xml comment for publicly visible type or ...
Fix in ASP.NET Core · Right-click the Visual Studio project / Properties / Build Tab · Insert warning number 1591 in the “Suppress...
Read more >Creating Web API in ASP.NET Core 2.0 - CodinGame
Step 03 - Add Models ; pragma warning disable CS1591 ; public static StockItem ToEntity(this PostStockItemsRequest request) ; pragma warning restore CS1591 ...
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
Hi, the issue was solved in the new
v3
version ofsetup-dotnet
action. By now I’m going to close this issue, If you have any additions or questions feel free to ping us.Workaround: If you supply the exact version, the warning does not appear.
Instead of
dotnet-version: 2.1.x
, usedotnet-version: 2.1.818