Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NetCore 3.1 support? #184

Open
MagicAndre1981 opened this issue Jun 18, 2020 · 6 comments
Open

.NetCore 3.1 support? #184

MagicAndre1981 opened this issue Jun 18, 2020 · 6 comments

Comments

@MagicAndre1981
Copy link
Contributor

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 MagicAndre1981 changed the title .Net Standard 2.x support? .NetCore 3.1 support? Jun 22, 2020
@MagicAndre1981
Copy link
Contributor Author

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

@mrworkman
Copy link
Collaborator

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

@MagicAndre1981
Copy link
Contributor Author

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
Copy link
Contributor Author

I tried to implement it with #188 @mrworkman

@MagicAndre1981
Copy link
Contributor Author

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
Copy link

BarsikV commented Jan 13, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants