You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Jupyter Extension team is planning on moving the notebook creation command from the jupyter extension to core VS Code since core already has support for notebooks without requiring the extension: microsoft/vscode-jupyter#9250
What this would mean for the .NET extension:
Creating a .NET interactive notebook would no longer be available from creating a Jupyter notebook which can currently happen two ways:
“Jupyter: Create New Jupyter Notebook” in the command palette
This one probably isn’t an issue since the .NET extension already has a “.NET interactive: Create New Blank Notebook” command.
This could possibly remove the only dependency on the Jupyter extension, unless there is another one I'm not aware of.
Let us know if there are any concerns/feedback for this change.
The text was updated successfully, but these errors were encountered:
The Jupyter Extension team is planning on moving the notebook creation command from the jupyter extension to core VS Code since core already has support for notebooks without requiring the extension: microsoft/vscode-jupyter#9250
What this would mean for the .NET extension:
Creating a .NET interactive notebook would no longer be available from creating a Jupyter notebook which can currently happen two ways:
“Jupyter: Create New Jupyter Notebook” in the command palette
This one probably isn’t an issue since the .NET extension already has a “.NET interactive: Create New Blank Notebook” command.
New file… -> Jupyter Notebook -> .NET interactive
For this, we would suggest that the .NET extension adds its own notebook type to the “New File…” menu, similar to https://github.com/microsoft/vscode/blob/32d40cf44e893e87ac33ac4f08de1e5f7fe077fc/extensions/ipynb/package.json#L56
This could possibly remove the only dependency on the Jupyter extension, unless there is another one I'm not aware of.
Let us know if there are any concerns/feedback for this change.
The text was updated successfully, but these errors were encountered: