Jon Sequeira

We're planning to move many features out of middleware in order to make things more flexible while also reducing the performance footprint of the built-in features that happen to be...

> Also found that calling `Invoke` on `ParseResult` does not call help or version, and reports `--help` and `--version` as errors. This is inconsistent and means I can't check if...

The extension isn't currently broken as far as I can tell. 

> It must stop being its own package though if i understand the docs correctly, because there has to be an attribute on the type that gets the custom formatting,...

Let me know if you want a hand or if you have feedback on the approach. And if you want to contribute F# sample code to document the convention-based approach,...

As far as I can see the code looks correct. Have you confirmed that the formatter source is being called at all? Here's an [example test](https://github.com/dotnet/interactive/blob/d5e7cb2979ba57f70e35b301dabbf0dde189c4e5/src/Microsoft.DotNet.Interactive.Formatting.Tests/FormatterTests.FormatterSources.cs#L28-L38). There's no F# equivalent...

If you can hit a breakpoint in the custom formatter source when it returns your formatter, then it's being detected correctly. If you can set a breakpoint in the custom...

When switching or upgrading extension versions, do you fully restart VS Code?

The latest version requires: * The .NET 9 SDK. (The runtime alone is not sufficient.) * A restart of VS Code.

The package has now been published on NuGet.org: https://www.nuget.org/packages/Microsoft.DotNet.Interactive.NamedPipeConnector