News

Microsoft Updates Jupyter Notebook Preview for .NET Core

Microsoft updated its preview project to enable working with Jupyter Notebooks in .NET Core with native programming languages C# and F#, providing new options for the traditional languages typically used, Python, R, Julia, Scala, etc.

Jupyter Notebooks are a popular approach to creating interactive environments -- like documents or canvases -- that can feature source code and markdown, or rich text formatting, and other media. The technology is often used for artificial intelligence, machine learning, Big Data and related projects.

Last November, Microsoft announced the first preview of the Jupyter-Notebooks-in-.NET-Core effort,

"The initial set of features we released needed to be relevant to developers, with Notebook experience as well as give users new to the experience a useful set of tools they would be eager to try," Microsoft said at the time.

Now (Feb. 6), the company announced Preview 2 of the .NET Notebook experience, along with a name change for Try .NET, an embeddable code runner that enables developers to explore .NET in the browser.

"As our scenarios grew in Try .NET, we wanted a new name that encompassed all our new experiences from the runnable snippets on the web powered by Blazor (as seen on the .NET page), to interactive documentation for .NET Core with the dotnet try global tool, to .NET Notebooks," said Maria Naggaga, senior program manager, in an announcement post. "Today we are announcing our official name change to .NET Interactive. .NET Interactive is a group of CLI tools and APIs that enable users to create interactive experiences across the web, markdown, and notebooks."

The effort now comprises global tools dotnet interactive (for .NET Notebooks) and dotnet try (for Workshops and offline docs, providing interactive markdown with a backing project), along with trydotnet.js -- an API not yet publicly available -- for documentation, currently consigned to internal Microsoft use. With the separation of efforts, there is now a .NET Interactive GitHub repo and a Try .NET repo.

Naggaga also announced:

  • New language support – PowerShell: "PowerShell notebooks combine the management capabilities of PowerShell with the rich visual experience of notebooks. The integration of PowerShell’s executable experience with rich text and visualization open up scenarios for PowerShell users to integrate and amplify their teaching, and support documents."
  • nteract.io support: "In addition to writing .NET Code in Jupyter Notebooks, users can now write their code in nteract. nteract is an open-source organization that builds SDKs, applications, and libraries that helps people make the most of interactive notebooks and REPLs. We are excited to have our .NET users take advantage of the rich REPL experience nteract provides,including the nteract desktop app." More on that is available in the ".NET Interactive with nteract" guidance.

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube