Ian Kemp

Sooo... is 1.0.0 on Choco ever gonna happen?

And still we wait... at this point @dahlbyk should remove the Choco install instructions from the README and delist the package from Choco, because it's causing more harm than good...

> I've been hoping to "do it right" with the 1.0 release on Chocolatey (e.g. fix install location) and honestly just haven't wanted to spend time on it. For a...

* I assume struck-through indicates "won't implement"? Would be useful to have that info at the beginning of the issue. * For the "won't implement" features, a one-liner description or...

> > `[assembly: Debuggable(/*Could not decode attribute arguments.*/)]` > > seems to be quite frequent recently, for me. Sometimes (!) it displays properly, then... not. > > This most likely...

This is a problematic one. It's already possible for end-users to achieve this by tweaking the Code Analysis rules for their projects, but obviously that's a pain. It's probably more...

Looking at the [Roslyn PR that added support for .editorconfig](https://github.com/dotnet/roslyn/pull/15029/files), it seems that: * Every analyzer gets passed a `Microsoft.CodeAnalysis.Diagnostics.SyntaxNodeAnalysisContext` that has an `Options` property of type `Microsoft.CodeAnalysis.Diagnostics.AnalyzerOptions`. * Then...

Just bumped my head against this. `unevaluatedProperties` is apparently supposed to solve the problem whereby you cannot use inheritance (`additionalProperties = false` together with `allOf`) so it would be great...

For anyone who is looking for a simple way to achieve this: ```csharp using NetTopologySuite.Geometries; using NetTopologySuite.IO; using GeoAPI.IO; public static class GeometryExtensions { /// /// Returns the EWKB representation...

Bumping this to find out whether there are plans to support the RC yet. I'm currently stuck using a different extension in the RC that isn't nearly as nifty as...