Have VS2022 installed, installed the Notebook editor extension and just opened the getting started folder and getting the following I was able to build C# Projects with my VS2022 and also C# Interactive windows work in VS2022
Kernel Failed To Start.
Cannot find a tool in the manifest file that has a command named 'dotnet-interactive'.
error: Cannot find a tool in the manifest file that has a command named 'dotnet-interactive'.
at StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__143`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Notebook.Utils.DetectKernelStatusService.<ExecuteTaskAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Notebook.Utils.RepeatedTimeTaskService.<>c__DisplayClass7_0.<<ExecuteAsync>b__1>d.MoveNext()
error: Cannot find a tool in the manifest file that has a command named 'dotnet-interactive'.
at StreamJsonRpc.JsonRpc.<InvokeCoreAsync>d__143`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Notebook.Utils.DetectKernelStatusService.<ExecuteTaskAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
[...]
Thanks for reporting!
I haven’t seen that one before - can you share what VS version you have installed and which .NET versions?
The extension should ensure the right versions of both are on your machine but perhaps it’s not sending commands to the right .NET version.
Sure, forgot to include that:
dotnet --info:
Hello!
So I found out what is happening but I haven't found out why.
Do you have any more messages in any of the output tabs in VS?
If you'd be up for trying something ... I'd try this:
I'm hoping we'll see the above but if we don't ... I'm hoping we'll get more information.
no, just the above message returning in loop. in the Output tab under DetectKernelStatueService
This didn't work for me, getting errors:
Checked my nuGet configuration at
%appdata%\NuGet\nuget.configpackageSources was empty
I added the following line :
And now everything is working after dotnet tool restore.
Awesome I was just about to ask!
These are the two nuget configs that I was going to ask to check:
Posting here as reference in the future.
We'll work to add our own nuget.config to the extension to make this more robust. Thanks!!
I wanted to add that my attempt to just include
<add key="nuget.org" value="https://api.nuget.org/v3/index.json" />to the file%appdata%\NuGet\nuget.configdidn't work.After looking at some of the other files mentioned I was able to resolve the issue by modifying the file as follows.
Hoping this can help others resolve this issue faster.
Hit the same error, but for me it turned out to be our corporate proxy blocking nuget.org - we typically get packages from an internal mirror. Adding http[s]_proxy environment variables worked as a workaround.
Confusingly I'd tried installing dotnet-interactive as both a global and local tool, so I wonder what else you need to reach out to nuget.org for?