Clarification on Deprecation Scope

[defufna]

Question

I am seeking clarification on the scope of the deprecation announced for March 27, 2026.

While it is clear that the Polyglot Notebooks extension for VS Code is being deprecated, the status of the .NET Interactive engine and the Jupyter Kernel is less certain. Specifically, the announcement mentions that "issues related to using .NET Interactive as a kernel in other Jupyter frontends will be closed."

Could you please clarify:

1. Is the .NET Interactive engine itself being deprecated? Will the underlying libraries and APIs continue to be maintained for other implementations?
2. Standalone Jupyter Kernel: Will the ability to install and use .NET Interactive as a kernel in standard Jupyter environments be officially deprecated or removed?

[claudiaregio]

Hi @defufna

.NET Interactive is also being deprecated which is why there is no recommendation to continue using .NET Interactive in other Jupyter frontends. Please reread the deprecation announcement for more details, your questions are answered in the announcement.

[alex4998]

Does it mean that C# Interactive will be dropped in Visual Studio as well? From the high-level perspective, it seems they should use the same engine behind. If no, and there is another engine built in the scope of Visual Studio, what will happen to that one?

[claudiaregio]

@alex4998 The C# interactive experience in Visual Studio is not powered by .NET Interactive.