.NetCore 3.1 support?

Question

.NetCore 3.1 support?

MagicAndre1981 opened this issue 4 years ago · comments

MagicAndre1981 commented 4 years ago

Is 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.

MagicAndre1981 · Answer 1 · Mon Jun 22 2020 21:24:40 GMT+0800 (China Standard Time)

ok, .net standard doesn't have OleDb support. So direct .NetCore 3.1 support is needed.

Stephen Workman · Answer 2 · Mon Jun 22 2020 21:34:49 GMT+0800 (China Standard Time)

Interesting, Oledb wasn't supported in .Net Core before... I'll have to look into it.

MagicAndre1981 · Answer 3 · Mon Oct 12 2020 18:50:43 GMT+0800 (China Standard Time)

ok, System.Data.OleDb package supports .net standard 2.0 and 3.1, but I have no idea how to test it. nunit console only has a beta to test .net core, but this fails.

In my application it looks like it works to load the Excel file and query data.

MagicAndre1981 · Answer 4 · Mon Oct 12 2020 19:20:32 GMT+0800 (China Standard Time)

I tried to implement it with #188 @mrworkman

MagicAndre1981 · Answer 5 · Wed Jan 06 2021 18:46:27 GMT+0800 (China Standard Time)

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.

BarsikV · Answer 6 · Fri Jan 14 2022 02:07:51 GMT+0800 (China Standard Time)

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 :)