Potential breaking changes in .NET Interactive dependencies

[colombod]

With the las published packages a lot of big changes in command parsing. This might create issues at runtime.

The interactive extension should update to latest if possible, also adopting the .dib based approach to install extension is advised, the interface based discovery is not ideal and introduces more issues, this extension could be built without dependencies on .NET Interactive by using convention based formatting and .dib to load the extension.

[kMutagene]

Thanks for the heads-up.

this extension could be built without dependencies on .NET Interactive by using convention based formatting and .dib to load the extension

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, the formatting code must be in the source of the core lib?

[jonsequitur]

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

[jonsequitur]

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, the formatting code must be in the source of the core lib?

As long as the only notebook behavior you want to customize is formatting (which appears to be the case with Plotly.NET), you don't need a separate assembly or a separate package at all, nor do you need to embed a .dib file to register formatters. You can follow the convention-based TypeFormatterSourceAttribute approach, remove the dependency on .NET Interactive libraries entirely, and therefore remove future version incompatibility problems.

You can see examples of this approach here.

[kMutagene]

@jonsequitur That's what i was thinking, thanks. I'll look into it

[jonsequitur]

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, I'm sure others would find it helpful.