Atle Rudshaug

See https://github.com/stephan-tolksdorf/fparsec/issues/45#issuecomment-552344681

+1 for removing the net45 target. I'm also struggling with this.

Ok, thanks! Will it require a lot of code change to make it netstandard2.0 or is it more or less a update project files job? I could probably contribute with...

That Linux provider would be nice to have. I can't seem to get the current one working. Just getting DLL not found exception whatever I do, but that's for another...

It would be awesome if this got fixed/merged. We've just got blocked by this as well when we removed net472 targets from our assemblies and only target netstandard2.0.

Could it use only the internal StrongNameKeyPair for both .NET 4.x and netstandard?

I would also like to keep comments on the same line. Mostly for Row/Column definition comments though. So it would be great with an option for those at least.

Yes, that would be better than having to use some special character. Thanks for a great tool btw.

> We do need an update to FAKE fairly soon that either takes out the Paket support, or makes it optional (is there a way to do this?), or brings...

Replacing ```csharp #I __SOURCE_DIRECTORY__ #r "paket: groupref Build //" #load @".fake/build.fsx/intellisense.fsx" #if !FAKE #r "netstandard" #endif ``` with the following ```csharp #r "nuget:Fake.Core.Process" #r "nuget:Fake.Core.Environment" #r "nuget:Fake.Core.SemVer" #r "nuget:Fake.Core.Target" #r...