-
Notifications
You must be signed in to change notification settings - Fork 75
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
2 year old prerelease? Project abandoned? #235
Comments
It's definitely not being actively developed at this point. It is in use in a fair number of projects though and is stable on the alpha release. The reason it's in that release channel was due to upgrading it to core m that branch can/should probably just be pushed out as is though. If it breaks because Reddit did something dumb it will definitely be fixed, but new features aren't really getting added. If you do put in a pull request though I'd happily merge it. |
Its not a pre-release now!! wooo!! haha |
The prerelease seemed to be compatible with .NET Framework & .NET Standard. AFAIK .NET Standard is compatible with everything so that would be ideal for targeting |
Might need to add in some more build targets |
@CrustyJew Is there an update on this? .NET Core is great, but can RedditSharp target .NET Standard (like before) so that implementers of RedditSharp don't have to change their projects from .NET Framework to .NET Core? |
@derekantrican I haven't had time or energy to look into retargeting it, but if you'd like to make a PR to add that support, I'd happily take a look and merge it. |
According to NuGet, the last stable version was published over 3 years ago - 1.1.14 on 8/23/2017. The last version published at all was over 2 years ago - 2.0.0-CI00075 on 11/20/2018 (and it is marked as a prerelease). Is the project currently stable enough to publish a new, stable version of the NuGet package? Is this project even still being developed? (I see the last commit was in February of this year so it seems like the project is still somewhat active but maybe packages are no longer being published?)
The text was updated successfully, but these errors were encountered: