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 Standard Version #5

Open
jag43 opened this issue Nov 30, 2018 · 7 comments · May be fixed by #20
Open

.Net Standard Version #5

jag43 opened this issue Nov 30, 2018 · 7 comments · May be fixed by #20

Comments

@jag43
Copy link

jag43 commented Nov 30, 2018

It would be great to have a .NetStandard version/target for the NeverBounceSDK project so we can consume this from our ASP.NetCore web applications.

@mmollick
Copy link
Contributor

@jag43 thanks for the suggestion. After some brief research, it certainly sounds like a good idea. However, we don't have any .Net gurus on our team to keep up with the ecosystem; so it may be some time until we get around to implementing this change. We would be open to PRs in the meantime.

@Yinamil
Copy link

Yinamil commented Sep 28, 2020

I know this is old, but I can look into doing this. I don't think I'd be able to devote a ton of time, but if I get the implementation over to a NetStandard project, I'm sure it can be easily maintained.
I'll have to have access to make pull requests without manually editing the files on the git repo itself. I added a fix to the Issue #12 but don't have write access so I couldn't push my branch. I had to manually edit the file in github itself, which is not ideal for converting this to .NetStandard.

@mmollick
Copy link
Contributor

@aareaux That would be much appreciated. My biggest concern is introducing backwards compatibility issues for existing users of the library.

In regards to write access, that shouldn't be necessary. You should be able to fork the project, commit your changes to your fork and then create a PR back to this project when you're done.

@Yinamil
Copy link

Yinamil commented Sep 29, 2020

@mmollick I would think you'd want to have a separate nuget for the .NetStandard version altogether. Could just name it something with 'AspNetCore' in it or something similar to distinguish between the two. If you want to create a new Git Repo for it, that would probably work better. I'll start working on porting it over.

@VagueGit
Copy link

Rather than calling the NetStandard version AspNetCore, which implies AspNetCore projects only and does not include other NetCore projects, might I suggest a name along the lines of NetCore version or Net5 version? NetCore is becoming Net5.

@pundj
Copy link

pundj commented Mar 10, 2021

Fix submitted in #16

@KeithHenry
Copy link

5 years later standard and core have merged since .NET 5

Current version of .NET is 7, PR #20 is a complete update to 7 along with lots of other fixes and .NET compatibility changes.

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