.NetCore 3.1 support?
See original GitHub issueIs it possible to get .Net Standard 2.x support? This would fix my NU1701 warning:
warning NU1701: Package 'LinqToExcel 2.0.0-PRERELEASE-2' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
.NET and .NET Core official support policy - Dot.net
For example, .NET 6 was originally released on November 8, 2021 and is supported for three years. But the actual end of support...
Read more >Microsoft .NET and .NET Core - Microsoft Lifecycle
Version Start Date End Date
.NET 7 Nov 8, 2022
.NET 6.0 (LTS) Nov 9, 2021 Nov 12, 2024
.NET 5.0 Nov 10, 2020 May 10,...
Read more >Microsoft .NET - endoflife.date
NET Core 3.1, these releases will happen every November and every other release will be LTS. LTS releases are supported for three years...
Read more >Microsoft Announces End of Support Date for .NET Core 3.1
NET 5 and 6, will reach its end of support on December 13, 2022. “.NET Core 3.1 will reach [the] end of support...
Read more >Microsoft to End Support for .NET Core 3.1 in December 2022
The long-term-support (LTS) version 3.1 of Microsoft .NET Core Framework is slated to go out of support on December 13th, 2022.
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 Free
Top 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
I gave it up now. I switched to ExcelMapper which is based on a pure managed excel reading library which is an advantage over LinqToExcel so that it doesn’t require Office runtimes.
Thanks man, that helped a lot and the libraries work in a very similar way 😃