-
Notifications
You must be signed in to change notification settings - Fork 345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting alot of Errors: "Kernel Failed To Start." #59
Comments
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! 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 I added the following line : <add key="nuget.org" value="https://api.nuget.org/v3/index.json" /> 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 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. |
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
The text was updated successfully, but these errors were encountered: