-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
cannot run "dotnet new console" #4605
Comments
Got the same Problem in toolbox on Linux Fedora Workstation 32 after installing
After that,
|
@TobiasNils something funny is going on here.
Did you install from the Microsoft repository? Fedora 32 includes .NET Core 3.1 in the main Fedora repositories. Installing
So that's the Fedora package. It installs to
That installs the bits built by Microsoft next to the bits built by Fedora. The two things are built differently. They may use different (native) compiler settings. They may be using slightly different verisons of runtime packages. This is something that no one really tests and might blow up at any moment. I would suggest using either the Microsoft packages for .NET Core, or the Fedora packages for .NET Core. Mixing them is probably not a safe thing to do. |
Good point, thanks for that. I had been following this guide. Installed the microsoft repo and then effectively with installing I just setup a new toolbox and went right to installing dotnet-sdk-3.1 and everything works :) |
@MrPaul3 can you please paste the output of |
EDIT: I don't know if this is the right place anymore, but in the toolbox container,
In the normal fedora shell, after installing from the fedora repositories, the whole tutorial works. |
@TobiasNils you might be hitting #3909. MSBuild passes all env vars in as MSBuild properties, and NuGet doesn't take kindly to a |
We have hit this in Fedora before too: https://pagure.io/dotnet-sig/dotnet-3-0/issue/9. Please feel free to describe how reading in all env vars (including |
It was indeed the |
This is based off the existing instructions for Fedora 31, with a few changes: - .NET Core (3.1) packages are part of the default package repositories in Fedora. No extra repositories need to be enabled to be able to install .NET Core 3.1. - Only 3.1 is available in the Fedora package repositories. So I added a comment suggesting users to install other SDK/Runtime versions manually. The other versions need to be a manual install because mixing dotnet packages from package repositories is a bad idea. For example, it might pull down sdk bits built by Microsoft but everything else built by Fedora. And that doesn't work: dotnet/core#4605 - The package manager troubleshooing comments are all specfic to the Microsoft repository. I have removed them.
This is based off the existing instructions for Fedora 31, with a few changes: - .NET Core (3.1) packages are part of the default package repositories in Fedora. No extra repositories need to be enabled to be able to install .NET Core 3.1. - Only 3.1 is available in the Fedora package repositories. So I added a comment suggesting users to install other SDK/Runtime versions manually. The other versions need to be a manual install because mixing dotnet packages from package repositories is a bad idea. For example, it might pull down sdk bits built by Microsoft but everything else built by Fedora. And that doesn't work: dotnet/core#4605 - The package manager troubleshooing comments are all specfic to the Microsoft repository. I have removed them. Fixes: 18038
This is based off the existing instructions for Fedora 31, with a few changes: - .NET Core (3.1) packages are part of the default package repositories in Fedora 32. No extra repositories need to be enabled to be able to install .NET Core 3.1. - Only 3.1 is available in the Fedora package repositories. So I added a comment suggesting users to install other SDK/Runtime versions manually. The other versions need to be a manual install because mixing dotnet packages from package repositories is a bad idea. For example, it might pull down sdk bits built by Microsoft but everything else built by Fedora. And that doesn't work: dotnet/core#4605 - The package manager troubleshooting comments are all specific to the Microsoft repository. I have removed them. Fixes: 18038
This is based off the existing instructions for Fedora 31, with a few changes: - .NET Core (3.1) packages are part of the default package repositories in Fedora 32. No extra repositories need to be enabled to be able to install .NET Core 3.1. - Only 3.1 is available in the Fedora package repositories. So I added a comment suggesting users to install other SDK/Runtime versions manually. The other versions need to be a manual install because mixing dotnet packages from package repositories is a bad idea. For example, it might pull down sdk bits built by Microsoft but everything else built by Fedora. And that doesn't work: dotnet/core#4605 - The package manager troubleshooting comments are all specific to the Microsoft repository. I have removed them. Fixes: 18038
This is based off the existing instructions for Fedora 31, with a few changes: - .NET Core (3.1) packages are part of the default package repositories in Fedora 32. No extra repositories need to be enabled to be able to install .NET Core 3.1. - Only 3.1 is available in the Fedora package repositories. So I added a comment suggesting users to install other SDK/Runtime versions manually. The other versions need to be a manual install because mixing dotnet packages from package repositories is a bad idea. For example, it might pull down sdk bits built by Microsoft but everything else built by Fedora. And that doesn't work: dotnet/core#4605 - The package manager troubleshooting comments are all specific to the Microsoft repository. I have removed them. Fixes: 18038
Same problem here, just after update to Fedora 32.
To Solve this, I uninstall all dotnet packages already installed. Then i disable all Microsoft dotnet repos (installed following Net Core web page instructions), then install package dotnet-sdk-3.1.x86_64 from Fedora 32. dotnet --info ouput it's now: **SDK de .NET Core (reflejando cualquier global.json): Entorno de tiempo de ejecución: Host (useful for support): .NET Core SDKs installed: .NET Core runtimes installed: To install additional .NET Core runtimes or SDKs: My only doubt is if Fedora will maintain this packages update with future updates or new versions. Anyway good work , Fedora |
Speaking as a fedora maintainer: I am sure we will. We do this for other compilers and runtimes like Clang, GCC, OpenJDK, Python and Ruby. I don't see why .NET Core will be an exception.
Thanks, but this wouldn't been possible without the help of all the amazing dotnet maintainers/developers on github here, especially the https://github.com/dotnet/source-build/ folks. |
Wonderfull to hear that!! And yes, thanks too to dotnet team. |
This is based off the existing instructions for Fedora 31, with a few changes: - .NET Core (3.1) packages are part of the default package repositories in Fedora 32. No extra repositories need to be enabled to be able to install .NET Core 3.1. - Only 3.1 is available in the Fedora package repositories. So I added a comment suggesting users to install other SDK/Runtime versions manually. The other versions need to be a manual install because mixing dotnet packages from package repositories is a bad idea. For example, it might pull down sdk bits built by Microsoft but everything else built by Fedora. And that doesn't work: dotnet/core#4605 - The package manager troubleshooting comments are all specific to the Microsoft repository. I have removed them. Fixes: 18038
The issue went to a different tangent it seems. I imagine that the Fedora issues are way different than that same error message on Windows. I'd be inclined to close this issue since we never heard back from the original author of the thread. |
Agreed on both counts. The Fedora 32 issue is unrelated to the Windows problem in the original post, and without more info there isn't anything we can do there. For the Fedora 32 problem, dotnet/docs#18347 has a link back to this thread as an example of a thing we should help with in the Microsoft Fedora 32 docs, and I don't see anything else in this thread that needs more tracking. |
Just piping in that I am also running into this on Ubuntu 16.04.4 x64. I don't have a global env variable
dotnet info:
|
@jensechu can you please get a binlog (http://aka.ms/binlog, so we can diagnose) and open a new issue? More info on that in #4491, which we unfortunately couldn't follow up on because we didn't get diagnostic info. It was similar: NuGet version issue, but |
@dagood Sure! I will do this when I wake up tomorrow, sorry. 😄 Thanks for your attention. |
Problem encountered on https://dotnet.microsoft.com/learn/dotnet/hello-world-tutorial/create
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.
C:\Users\Rick\Documents\VSCodeNetCoreTest> dotnet new console -o myApp
It was not possible to find any installed .NET Core SDKs
Did you mean to run .NET Core SDK commands? Install a .NET Core SDK from:
https://aka.ms/dotnet-download
THIS IS THE ERROR . I HAVE ALREADY INSTALLED .NET CORE SDK COMMANDS BUT THEY ARE STILL SHOWING
The text was updated successfully, but these errors were encountered: