Skip to content
This repository has been archived by the owner on Feb 10, 2021. It is now read-only.

Consider supporting .Net core #145

Closed
haf opened this issue Dec 12, 2016 · 2 comments
Closed

Consider supporting .Net core #145

haf opened this issue Dec 12, 2016 · 2 comments

Comments

@haf
Copy link
Contributor

haf commented Dec 12, 2016

https://icanhasdot.net/result?github=logary~2Flogary

@haf
Copy link
Contributor Author

haf commented Feb 5, 2018

We've moved Logary to .Net core now. So this is still relevant.

@pblasucci
Copy link
Contributor

I’m torn on which way to go with this one. I can see three possible options:

  1. Keep the current setup but address .NET Standard with multi-targeting
  2. Move the whole repo, as-is, to .NET Core and require higher minimum versions from consumers.
  3. Write a new API entirely on .NET Core

Obviously, I like the 3rd option the best, but I’ve no time for it. The 1st is the most expedient, but does nothing for the long-term maintenance issues. And the 2nd option sort of splits the difference between the others.

I’ve been hoping someone would just “make it happen” (wink). But I guess I’ll have to sort it one of these days... probably by electing the 2nd option above.

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

No branches or pull requests

2 participants