ML.NET Updates & Announcing Notebooks in Visual Studio

Bri Achtman

ML.NET is an open-source, cross-platform machine learning framework for .NET developers that enables integration of custom machine learning into .NET apps.

In this post, we’ll cover the following items:

  1. Model Builder updates
  2. Progress on addressing ML.NET pain points
  3. Get started and resources

Model Builder updates

Notebook Editor in Visual Studio

Interactive Notebooks are used extensively in data science and machine learning. They are great for data exploration and preparation, experimentation, model explainability, and even education.

Last year, .NET Interactive Notebooks were announced, and you can currently use .NET Interactive Notebooks in VS Code as an extension.

After talking to customers, the team decided to experiment with Interactive Notebooks in Visual Studio which has resulted in the new Notebook Editor extension!

Screenshot of Notebook with a graph in Visual Studio

Getting started with Notebook Editor

Notebook Editor is only available in Visual Studio 2022 starting with Preview 4 and is currently offered as an experimental (preview) extension.

To try it out, you should first:

  1. Install Visual Studio 2022 Preview 4 (or newer).
  2. Install the Notebook Editor extension from the Visual Studio Marketplace.

Then, there are two entry points to get started with Notebook Editor in Visual Studio.

The first entry point is from ML.NET Model Builder, where you can get a generated Notebook with content based on your own data and model.

To get a Notebook from Model Builder:

  1. Install the latest version of Model Builder for VS 2022.
  2. Train a model with Model Builder and go to the Consume step.
  3. Under Project templates, add the Notebook to your solution. Screenshot of Consume step in Model Builder with Notebook Project Template
  4. Double click on the .ipynb file that is now in the Solution Explorer to open the Notebook in Notebook Editor. Screenshot of the Notebook file in Solution Explorer, ML.NET and Model Builder October Updates














The generated Notebook from Model Builder contains:

  • The training pipeline for the model chosen by Model Builder so that you can see how your model was trained and easily re-train
  • Plots and graphs for data exploration and model explainability techniques so that you can more easily understand and explain your data and model

Screenshot of the Notebook generated by Model Builder, ML.NET and Model Builder October Updates

The second entry point for Notebooks is to simply add a new Notebook from the Add New Item dialog.

  1. Right click on your project in the Solution Explorer.
  2. Select Add > New Item…
  3. In the Add New Item dialog, select Notebook and add it to your project. Screenshot of Notebook in Add New Item dialog, ML.NET and Model Builder October Updates

This creates a blank Notebook with no content. You can try adding some C# code and running a cell in the Notebook like this:

Screenshot of System.Console.WriteLine("Hello World") in a Notebook cell

This is the first version of Notebooks in Visual Studio! If you have any feedback, issues, or questions about Notebook Editor or Notebooks in Visual Studio, please file an issue in our GitHub repo.

Consumption code improvements

After you train a model in Model Builder, the Consumption file is generated and added to your project. This Consumption file contains a Predict() method which you can use to make predictions with your model in your end-user application.

This method abstracts away several steps that are needed to consume an ML.NET model:

  1. Initializing an MLContext
  2. Loading the model
  3. Creating a PredictionEngine
  4. Using the PredictionEngine and the model to make the prediction on the input data

In the previously generated model consumption code, these steps all happened inside the Predict() method, meaning that these all happened every time the Predict() method was called. This resulted in decreased performance on each prediction.

So, we updated the code to make it a lot more efficient where all of these steps only happen once when using the Predict() method.

The new code is demonstrated below:

public static ModelOutput Predict(ModelInput input)
    var predEngine = PredictEngine.Value;
    return predEngine.Predict(input);

private static PredictionEngine<ModelInput, ModelOutput> CreatePredictEngine()
    var mlContext = new MLContext();
    ITransformer mlModel = mlContext.Model.Load(MLNetModelPath, out var _);
    return mlContext.Model.CreatePredictionEngine<ModelInput, ModelOutput>(mlModel);

Read more about all of this month’s updates in the Release Notes.

Progress on addressing ML.NET pain points

As mentioned in the last ML.NET blog post, the following items were found as top pain points or blockers in this year’s ML.NET customer development:

  1. Small ML.NET Community
  2. Afraid Microsoft will abandon the framework
  3. Lack of / quality docs and samples
  4. Lack of deep learning support
  5. Specific ML scenario or algorithm not supported by ML.NET

Below we have outlined the steps we’ve taken so far and progress we’ve made in each area.

Small ML.NET Community

The team continues to host the Machine Learning .NET Community Standup every other week to talk about what we’re working on and to educate and engage with the community. We’ve also added a new story to the ML.NET Customer Showcase and are working on adding more.

We are also encouraging contributions to ML.NET. The first good issue and up-for-grab issues on GitHub are a great place to start!

Additionally, following the previous .NET monthly themes of F#, Razor, and IoT, October will be focused on machine learning! The team is currently planning out lots of machine learning and ML.NET content and is looking forward to working with the community on this.

Afraid Microsoft will abandon the framework

ML.NET is .NET, and to make it feel more a part of .NET, we’ve decided to align with the .NET release schedule. This means that we will ship our next version of ML.NET (v1.7.0) with .NET 6.0 in November 2021 and will ship subsequent major releases (ML.NET 2.0, 3.0, etc.) with major releases of .NET. We will ship production-ready preview version releases in between so that we can continue adding new features to the framework throughout the year.

We are also taking steps to organize the dotnet/machinelearning repo and keep it up to date. We are currently revising our triage processes so that we can address your issues and feedback faster. Issues will be linked to version releases in the Projects section of the repo so you can see what we’re actively working on and when we plan to release.

Check out the roadmap to see what we have planned for ML.NET this year.

Lack of / quality docs and samples

We have invested more resources into content development to make sure our Docs stay up to date and that we add documentation for new features faster as well as add more relevant samples.

@luisquintanilla (Microsoft content developer) and @jwood803 (ML.NET community member and newly contracted docs/samples developer) have both been working hard to ensure that we increase the quality of ML.NET documentation. They have set several goals, including reducing the average days to close Docs issues and publishing documentation for new features no more than two weeks after a new feature is released.

In the past two months, 19 articles have been updated, and a new article on how to label images for object detection has been added. This month, the team is working on adding two new tutorials for image classification and recommendation in Model Builder to Docs as well as updating the samples to the newest version of ML.NET.

You can file issues and make suggestions for ML.NET documentation in the dotnet/docs repo and for ML.NET samples in the dotnet/machinelearning-samples repo.

Lack of deep learning support

This past year we’ve been working on our plan for deep learning in .NET, and now we are ready to execute that plan to expand ML.NET’s deep learning support.

As part of this plan, we will:

  • Make it easier to consume ONNX models in ML.NET using the ONNX Runtime (RT)
  • Fully support and productionize TorchSharp for building neural networks in .NET
  • Build a bridge between TorchSharp and ML.NET

Read more about the deep learning plan and leave your feedback in this tracking issue.

Specific ML scenario or algorithm not supported by ML.NET

We have added Named Entity Recognition to the roadmap which has been a highly requested scenario since ML.NET was released.

The deep learning plan will also enable a variety of other scenarios so that you can train custom models for object detection, NLP tasks, and more in .NET.

If there is still a scenario or algorithm missing that is not covered in the roadmap, please let us know by filing an issue.

Get started and resources

Learn more about ML.NET and Model Builder in Microsoft Docs.

If you run into any issues, feature requests, or feedback, please file an issue in the ML.NET API repo or the ML.NET Tooling (Model Builder & ML.NET CLI) repo on GitHub.

Join the ML.NET Community Discord.

Tune in to the Machine Learning .NET Community Standup every other Wednesday at 10am Pacific Time.


Discussion is closed. Login to edit/delete existing comments.

  • shanyou zhang 0 is 404

    right url:

    PS C:\Users\geffzhang\tke> dotnet tool install -g –add-source “” Microsoft.dotnet-interactive

    欢迎使用 .NET 6.0!

    SDK 版本: 6.0.100-rc.1.21463.6


    .NET 工具会收集用法数据,帮助我们改善你的体验。它由 Microsoft 收集并与社区共享。你可通过使用喜欢的 shell 将 DOTNET_CLI_TELEMETRY_OPTOUT 环境变量设置为 “1” 或 “true” 来选择退出遥测。

    阅读有关 .NET CLI 工具遥测的更多信息:

    已安装 ASP.NET Core HTTPS 开发证书。
    若要信任该证书,请运行 “dotnet dev-certs https –trust” (仅限 Windows 和 macOS)。

    了解 HTTPS:

    在 GitHub 上报告问题和查找源:

    使用 “dotnet –help” 查看可用命令或访问:

    C:\Program Files\dotnet\sdk\6.0.100-rc.1.21463.6\NuGet.targets(130,5): error : 无法加载源 的服务索引。 [d:\Temp\o2zvszea.ovl\restore.csproj]
    C:\Program Files\dotnet\sdk\6.0.100-rc.1.21463.6\NuGet.targets(130,5): error : 由于目标计算机积极拒绝,无法连接。 ( [d:\Temp\o2zvszea.ovl\restore.csproj]
    C:\Program Files\dotnet\sdk\6.0.100-rc.1.21463.6\NuGet.targets(130,5): error : 由于目标计算机积极拒绝,无法连接。 [d:\Temp\o2zvszea.ovl\restore.csproj]

    • 你尝试安装预览版,但未使用 –version 选项来指定该版本。
    • 已找到具有此名称的包,但是它不是 .NET 工具。
    • 无法访问所需的 NuGet 源,这可能是由于 Internet 连接问题导致。
    • 工具名称输入错误。


    • Bri AchtmanMicrosoft employee 0

      Good catch! It’s been updated now. 🙂

  • MgSam 0

    Glad to see DataFrame is not dead and you guys are still planning to do more work on it.

  • Larry Bowden 0

    It would be a good start to be able to easily compile TorchSharp. Its difficult and time consuming due to many third party libraries and version constraints.

  • Matías 0

    Great news guys! Love to see the TorchSharp bridge!… Keep up the good work!

  • James Foye 0

    I will never touch this because of pain point #2.

    • Jake RadzikowskiMicrosoft employee 0

      Can you elaborate? We are dedicated to empowering .NET Developers to leverage machine learning! We’d love to have you try it out!

      • Yong Du 0

        Very glad to see the new release. Almost lost my patience when Microsoft.Data.Analysis 0.4.0 was moving to nowhere in more than 1 year.

Feedback usabilla icon