.Net sdk issue when i try to run it in cmd

Question

Gavindu Wijesinghe 1

**

I installed .net sdk5.0.400 win x64 on my laptop. But when I type dotnet --version on cmd there is a message saying that I don't have a .net sdk installed. What should I do?

**

RLWA32 49,461 Reputation points

2021-08-30T10:24:24.847+00:00

It appears that your system has the .Net 5.04 sdk installed twice -- once during the installation of Visual Studio and then separately. This is what my system with VS2019 shows --
Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2021-08-30T15:52:33.113+00:00

"your system has the .Net 5.04 sdk installed twice" is perfectly normal. Microsoft intentioinally packs .NET Core SDK in that way.
RLWA32 49,461 Reputation points

2021-08-30T16:04:11.65+00:00

Well, my installed programs list only shows the one .Net 5.04 SDK that was installed with Visual Studio 2019. The image posted by the questioner shows two of them.

And a 32-bit command prompt produced the following results -

RLWA32 49,461 Reputation points

2021-08-30T10:24:24.847+00:00

It appears that your system has the .Net 5.04 sdk installed twice -- once during the installation of Visual Studio and then separately. This is what my system with VS2019 shows --
Lex Li (Microsoft) 6,037 Reputation points Microsoft Employee

2021-08-30T15:52:33.113+00:00

"your system has the .Net 5.04 sdk installed twice" is perfectly normal. Microsoft intentioinally packs .NET Core SDK in that way.
RLWA32 49,461 Reputation points

2021-08-30T16:04:11.65+00:00

Well, my installed programs list only shows the one .Net 5.04 SDK that was installed with Visual Studio 2019. The image posted by the questioner shows two of them.

And a 32-bit command prompt produced the following results -

Answer 1

Lex Li (Microsoft) 6,037 Microsoft Employee

Take a look at the file paths in your screenshot and you can see they all point to C:\Program Files (x86).

That indicates you launched a 32 bit command prompt, which won't be able to locate 64 bit SDKs you installed on this machine.

The solution is to open a 64 bit command prompt from C:\Windows\system32\cmd.exe.