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

.NET Framework v4.6 is too restrictive #3

Closed
polewskm opened this issue Oct 28, 2016 · 2 comments
Closed

.NET Framework v4.6 is too restrictive #3

polewskm opened this issue Oct 28, 2016 · 2 comments
Assignees

Comments

@polewskm
Copy link

This library is great especially since it targets .NET Standard and .NET Framework but your latest version specifically targets .NET Framework v4.6 which most people have not adopted yet. Would it be possible to lower the runtime version down to v4.5.1? It should be okay since you are not using anything specific from the newer runtime.

@richardtallent
Copy link
Owner

Sure thing. I'm working on a fix to the PostgreSql logic and reorganizing the code a bit to work better for DI, so there should be a new version available soon.

@richardtallent
Copy link
Owner

I finally had a chance to work on this a bit, fixing a logical issue in the PostgreSql implementation, upgrading to .NET Core 1.1 (just released), reorganizing the API, and as requested, moving back to 4.5.1. This was more difficult than I hoped because 4.6 has the ToUnixTimeMilliseconds / FromUnitTimeMilliseconds I wanted for a new variation. Please be sure to check out the new API, some changes will be needed.

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

No branches or pull requests

2 participants