-
Notifications
You must be signed in to change notification settings - Fork 20
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
Rider can't detect dotnet sdk #21
Comments
@heuristicAL |
Slight typo there, should be I also forgot to mention that I'm running on Macos so Thanks for the suggestion though! |
However, I did encounter an issue with other tools not being able to find dotnet due to export DOTNET_ROOT
DOTNET_ROOT="$(asdf where dotnet-core)" |
So setting the vsersion of dotnet manually worked but that seems.... not ideal? Since we aren't actually using asdf to set the version for Rider. I personally did not have any problems using the set-dotnet-home script, although I use zsh, not bash. Are you sure you're using it correctly? I did not source it, I just used executed it like they say to do in the readme: |
I think Rider searches for MSBuild in the path that contains Created ticket with JetBrains:
|
Yes, Rider try to detect SDK in folder contains dotnet binary. I will try to fix it. |
@mfilippov 👋 Any progress on this? It is still an open bug: https://youtrack.jetbrains.com/issue/RIDER-56411 |
The issue got related to another issue at jetbrains. |
@thewoolleyman I hope to fix it in the Rider 2020.2 scope. |
Replicating my comment from Jetbrains Ticket here:Since then I have come to believe that dotnet and asdf are not compatible with each other and that this problem is not caused by Jetbrains Rider. The recommend location to install dotnet to is: The recommend location to symlink to is: To quickly install both LTS and Current is:
When I installed dotnet outside the recommended location, I always got errors with some MSBuild scripts. Example errors:
Maybe it would work if asdf would have some kind of I still think
|
My response on the Jetbrains issue:
I don't think this is true.
Manually installing to a hardcoded location is not a viable option, if you need to frequently switch between multiple projects which use different versions of the dotnet toolset. This is not an issue for other Bottom line, since I can run dotnet apps fine via the command line with an asdf-managed version of dotnet, I don't see any reason Rider shouldn't be able to support this as well. |
Lets keep the discussion going at Jetbrains. I will test with asdf to see if the errors I mentioned are also there when using just the CLI.
|
JetBrains says: "Fixed in Branch" 🥳 |
Please test with Rider Next EAP 2021.2. |
Rider EAP1 shipped this week. |
I will test today! |
I did some tests and the results look promising. I would like to invite others to test this as well. |
I have the same trouble, but I change the default location of sdk path with dotnet MSBuild variable |
Jetbrains has since marked https://youtrack.jetbrains.com/issue/RIDER-56411 as fixed but looking through the thread I still unsure on how to go about setting up Rider to work with ASDF. Anyone have specific steps? |
To be honest...is there really a use case for using asdf to manage dotnet? I mean...using just dotnet, you can run multiple sdks on your machine, have projects target specific framework versions and nuget packages. I don't see what asdf could bring to the table. |
I think so,
You question is less, is ASDF useful with .NET, more is it useful with anything, because it's possible to install multiple Node, JDK, Python, etc versions. In my use case, I would say yes. |
I don't agree. Other languages work differently from dotnet. There |
Rider still can't find it on Linux, even after I give it the path to it in the settings. It says "Check that .NET Core SDK is installed in '/usr/bin'. " But .Net installs to '/usr/share/dotnet/sdk' by default currently. I entered the correct path in the Toolset and Build settings. But it still says "Check that .NET Core SDK is installed in '/usr/bin'. " |
Global tools execution was failing because it couldn't find .NET location, I'm so happy you wrote this comment. You saved me from headache. |
even though the path is set to
~/.asdf/shims/dotnet
, Rider says it cannot find the dotnet sdk. I don't know if this is something that others have encountered and if its even an asdf-dotnet-core issueThe text was updated successfully, but these errors were encountered: