Skip to main content

Polyglot Notebooks–Update NuGet dependencies

In this post I'll give a short introduction about the Polyglot Notebooks extension in VS Code and focus one specific element; how to update the NuGet dependencies inside your code cells when using this extension.

Let’s dive in…

Polyglot Notebooks in VS Code

As opposed to traditional notebooks that are typically used with Python, the Polyglot Notebooks VS Code extension allows you to use multiple programming languages natively all in the same notebook . It supports languages like C#, F# but also SQL, JavaScript, Powershell and more.

The Polyglot Notebooks extension is powered by .NET Interactive, an engine and API for running and editing code interactively.

A notebook is a combination of code and documentation in the same file. After installing the extension, you can open a notebook(recognizable by the ipynb extension) and execute the coding blocks by clicking on ‘play’:

Using NuGet packages inside your code blocks

Inside a code block you are not limited to C# code inside the BCL but you can reference NuGet packages using the following syntax:

#r “nuget: <package name>”


Updating NuGet packages

In the screenshot above, you can see that I’m using an older version of the Semantic Kernel package. I updated the package(s) by changing the nuget version in the code cell:

However when I tried to run the code again, it failed with the following error message:

Error: <Package Name> version <version number> cannot be added because version <previous version number> was already added

To get rid of this error, a restart of the current notebook’s kernel is required:

  • Hit control-shift-p to open the Command dropdown
  • Search for the Restart kernel command and hit <enter> to execute it

More information

Announcing Polyglot Notebooks! Multi-language notebooks in Visual Studio Code - .NET Blog (microsoft.com)

Polyglot Notebooks - Visual Studio Marketplace

dotnet/interactive: .NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before. (github.com)

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...