Missing dotnet path pop-up should link to preferences

[premanir]

I am getting the below error message while creating a project in DotNet

There is no path to the DotNet command, please specify the correct path in the preference

Please help me to resolve the issue

[LucasBullen]

Go to the .NET Core page in your preferences. There you should be able to put the path to your dotnet executable. Must be greater than v2.0.

[mickaelistria]

@LucasBullen is right, and I think it's not really an issue. That said, we can use user question as an opportunity to guess a good change: link from popup to the Preference Page. I've retitled the issue.

[LucasBullen]

There is already a link for when there is no set path and for when the path is the wrong version.

@premanir Did you see this popup with the link to preferences or did you find a different popup?

[premanir]

Hi,

I navigated to Preferences screen and tried to gave the path of .NET executable of version greater than 2.0 Currently my .NET version is 4.7.2 which is actually the latest one So, when I tried to browse the path of that executable I am getting the below error message Please help me to resolve the issue Please find the below screenshot for reference

[mickaelistria]

aCute is initially targeting dotnet-core, and may have some glitch with other flavours of the dotnet package. Are you sure the path you gave it the one to the location where dotnet command is placed? It seems like you gave it the path to the dotnet installer instead, and that Eclipse aCute actually starts the installer instead of retrieving the version when starting it.

[premanir]

Yes, you got it correct. I have set the executable path rather then setting the command path Please help me to understand from where can I get the .NET command path

[LucasBullen]

I haven't tested this on windows, but from a bash shell you can try which dotnet, where dotnet, or where dotnet or from the Windows PowerShell you can try where.exe dotnet or get-command dotnet. If any of these work, do tell me and we will incorporate it into the default searching technique

[premanir]

I tried with both the commands in PowerShell "where.exe dotnet" and "get-command dotnet" But none were able to find the path where dotnet command is located

[mtripakis]

I think that with a default installation, it should be here: C:\Program Files\dotnet\dotnet.exe Just make sure you have .net core installed. If not, you can download it here: https://www.microsoft.com/net/download/windows

[premanir]

Correct me if I am wrong but .NET Core is quite old and I am currently sitting on .NET 4.7.2 Will it affect my environment in any way if I proceed with my .NET Core installation ?

[mtripakis]

They are supposed to be different products and work independently. So I think it shouldn't, but no promises about that "affect in any way" as I currently don't use either for my main development and cannot test it. From previous limited experience, in .net languages you target a framework and version for your application to build against, so, just choose .net framework. (By the way, Core is not older, it just targets cross platform development as opposed to .Net Framework which has broader capabilities but is Windows specific.) Again, hunch says you should be fine, but no first-hand recent experience to verify that. (If you don't want to try and find out and need a more trustworthy/detailed answer, you should probably try asking on stack overflow or a .net technology oriented forum)

[premanir]

Yes, I tried with the path of .NET Framework but no luck there Thanks for the clarification, I will proceed with CORE installation anyway as I already got the hint above acute is compatible with core and there might be some possibility to face glitches on the version above I navigated the link you have shared Which one out of the two displayed in screenshot below should I proceed with installation

1. .NET Core 2.1 SDk
2. .NET Core 2.1 Runtime

[mtripakis]

For development you need the SDK (stands for Software Development Kit).

[mickaelistria]

I'm closing this issue as there is no bug, and the UX seems relatively good. I don't think there is much more aCute can do to help on this story. If you have some suggestions, feel free to create new tickets.