Ricardo Amores Hernández

Yep, I'm afraid that's a flaw in the library: it does not saves where the comments, or any other construct, for the matter, are located in relation with the rest...

Sorry, missed your question about the wrapping spaces in key/value pairs, you can change the character to use as spacer at `IniData.Configuration.AssigmentSpacer = '';` https://github.com/rickyah/ini-parser/blob/development/src/IniFileParser/Model/Configuration/IniParserConfiguration.cs#L199

I'm afraid there is no way to do what you want to do right now.

@MrDave1999 a fork may not be necessary. Please take a look to what I wrote here: https://github.com/rickyah/ini-parser/issues/237 Also, if you would like to reopen the PR I would gladly merge...

DotnetCore 3.1 was released literally last week. I do not have the bandwidth to update the library so quickly, sorry. If you happen to start working on 3.1 compatibility, PRs...

@ichilver as a workaround can you get along with adding the library source code directly to your project?

I think I didn't considered using multiple comment characters. I'll take a look at your improvements, thanks

Hey @ravensorb thanks for the contribution! The netcore3.1 target framework is making the mono build, is adding that framework a must?

I'm trying to reduce the amount of namespaces, true, but I probably won't reduce it to one namespace either. There is no reason for the high amount of namespaces other...

I'll take a look at it