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

Is this still acitve? #231

Open
JakobFerdinand opened this issue Apr 15, 2021 · 9 comments
Open

Is this still acitve? #231

JakobFerdinand opened this issue Apr 15, 2021 · 9 comments

Comments

@JakobFerdinand
Copy link

Is this project still acitve?
I can see new issues and contributions but there is no new release since 2017?
Releasing the netstandard version of the library would be an important improvement.

@theKBro
Copy link

theKBro commented Jun 8, 2021

+1
a new version would be great!

@theKBro
Copy link

theKBro commented Jul 12, 2021

@rickyah ?

@MrDave1999
Copy link

It seems that the author of this library is not active. I have made a PR for them to add support for .NET Standard 2.1.

At the moment I have published the package on NuGet.

@dennys
Copy link

dennys commented Nov 3, 2021

@MrDave1999 , I upgrade to use ini-parser-netcore3.1, but it seems not support FileIniDataParser.WriteFile().
Is there any solution to write configuration to file?

@MrDave1999
Copy link

@dennys
Copy link

dennys commented Nov 8, 2021

@dennys Install this package: https://www.nuget.org/packages/ini-parser-netstandard/2.5.2

It works, thanks.

@briansilvers
Copy link

briansilvers commented Nov 13, 2021

So the version 3.0 of this code that I downloaded seems to have fixed the parsing problems that I was experiencing. I pulled down the code and built it and installed the nuget package on my project. is someone taking over this repo and has anybody reached out to @rickyah to see if we can help with it?

@MrDave1999
Copy link

MrDave1999 commented Nov 20, 2021

@briansilvers It seems that @rickyah lost interest in this project. We can continue this project as a fork.

@rickyah
Copy link
Owner

rickyah commented Nov 20, 2021

@MrDave1999 a fork may not be necessary. Please take a look to what I wrote here: #237

Also, if you would like to reopen the PR I would gladly merge it. In any case, thanks a lot for spending your time fixing the problems

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

6 participants