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

Npgsql 3.1.9 #392

Open
yallie opened this issue Dec 19, 2016 · 3 comments
Open

Npgsql 3.1.9 #392

yallie opened this issue Dec 19, 2016 · 3 comments

Comments

@yallie
Copy link
Contributor

yallie commented Dec 19, 2016

PostgreSQL 3.x driver is a major rewrite and it doesn't support .NET 4.0 anymore.
It's generally faster and better but it's not 100% compatible with earlier versions.
Here's the related discussion about dropping the .NET 4.0 support.

I'm considering the upgrade of the PostgreSQL driver package, but it means that
BLToolkit assembly itself should be upgraded to .NET 4.5 in order to use it.
Can we go for it?

Anyone here using BLToolkit with PostgreSQL?
Any thoughts/comments? :)

@ili
Copy link
Collaborator

ili commented Dec 20, 2016

This is very bad. Because .Net 4 is Windows XP.
I think to use new driver new package would be needed, or to do like in linq2db - dynamic types and assemblies resolve.

@yallie
Copy link
Contributor Author

yallie commented Dec 20, 2016

I believe more and more ADO.NET providers will drop .NET 4.0 support soon,
because neither .NET, nor Mono doesn't support it anymore.
Perhaps it's the time to add a BLToolkit.45 assembly to support newer drivers.

dynamic types and assemblies resolve

Well, it won't work on XP anyway :)

I think that having a separate BLToolkit.45.csproj targeting .NET 4.5
would need less maintainance than dynamic loading and assembly resolution.

@ili
Copy link
Collaborator

ili commented Dec 20, 2016

Copy & Paste from linq2db :))) i think it is about 2-3 workdays with testing...
In other way it would be needed to have plenty of projects..

And all the problems are about Windows XP... MS don't want to support it, but i should =\

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

2 participants