System.IO.FileNotFoundException when open C# notebook in Jupyter

[bhrnjica]

I have started to test C# Jupyter Notebook after I followed the instruction how to install Jupyter .NET Kernel on my local machine. I have successfully installed the latest version of Anaconda with Python 3.7. Once the Anaconda installed , I opened Anacoda CMD prompt and installed 'dotnet try’ tool from the instruction document.

Everything was installed without any errors. I have opened Jupyter Notebook and tried to open MLNET-Jupyter-Demo.ipynb predefined sample. As soon I run the first cell in the notebook, the .NET kernel throws the exception in the cmd:

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.AspNetCore.Mvc.Components.Prerendering
, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.

Before and after the bug appeared, I could successfully run Python Notebook.

I attached the full exception in the bug report.

Did this error occur while using dotnet try or online?

• [x] dotnet-try
• [ ] online

What kind of error was it?

• [ ] User Interface (UI): For example the output never displayed
• [] Service Error: For example "The service is temporarily unavailable. We are working on it"
• [x] Other: A connection to the notebook server could not be established. The notebook will continue trying to reconnect. Check your network connection or notebook server configuration.

Screenshots

If applicable, add screenshots to help explain your problem.

Please complete the following:

• OS
  • [x] Windows 10 and Windows Server 2019 Datacenter
  • [ ] macOS
  • [ ] Linux (Please specify distro)
  • [ ] iOS
  • [ ] Android
• Browser
  • [x] Chrome and Microsoft Edge Beta , Firefox
  • [ ] Edge
  • [ ] Safari

NETKernel Exception.txt

[jonsequitur]

Thanks, @bhrnjica. Can you also provide the output of the following two command lines:

> dotnet --info
> dotnet-try --version

[bhrnjica]

Sure, here are screenshots with the commands:

[bhrnjica]

After update to the latest version of ‘dotnet try’ tool (1.0.19507.38+911bbcb1cbe963268623f95b76cad450006be78b), everything works perfectly.