Can't build fresh proj on UE 5.3 on Rider

The SDK 'Microsoft.NET.SDK.WorkloadAutoImportPropsLocator' specified could not be found.

Could not resolve SDK "Microsoft.NET.SDK.WorkloadAutoImportPropsLocator". Exactly one of the probing messages below indicates why we could not resolve the SDK. Investigate and resolve that message to correctly specify the SDK.

The NuGetSdkResolver did not resolve this SDK because there was no version specified in the project or global.json.

MSB4276: The default SDK resolver failed to resolve SDK "Microsoft.NET.SDK.WorkloadAutoImportPropsLocator" because directory "C:\Program Files\Epic Games\UE_5.3\Engine\Binaries\ThirdParty\DotNet\6.0.302\windows\sdk\6.0.302\Sdks\Microsoft.NET.SDK.WorkloadAutoImportPropsLocator\Sdk" did not exist.

Hey guys, I’m having this issue with a brand new cpp ThirdPerson project in UE 5.3, I can’t build it cause of it but no issue with the 5.2 even on other projects.

I know that is just a file missing, but it’s a fresh install of 5.3 and a new proj so it shouldn’t happen, I’m wondering if old folders had to be deleted, like for the UnrealBuilderTool.

I can’t find much on internet, does anyone have any insight? Thx!

7 Likes

Verify your installation (using the Epic Launcher).

Or install it by hand.

Both of them did it already, as I said the 5.2 keeps working fine so the SDK is installed, only the 5.3.
Same if I change engine version from/to 5.2/5.3

I have not that folder too.

Sin tĂ­tulo

And i can compile well.

Try this command…

call "C:\Program Files\Epic Games\UE_5.3\Engine\Build\BatchFiles\Build.bat" MyProjectEditor Win64 Development "C:\Users\ivane\Desktop\UnrealProyects\MyProject\MyProject.uproject" -waitmutex -NoHotReload

Maybe you have a wrong version of MSBulid configured

I tried different ones from the list, but they all have other problems.
The one selected is the only one working with all the past versions of the engine.

Do you updated the minimal requirements installed for 5.3 version?

if is not this, i have not more ideas… i’m sorry!!

Yes, the hardware is not a problem and I just tried with VS Studio 2022 and there’s no problem.
Thank you for the suggestions

1 Like

I have not this installed… i don’t know if it is related
it is my last idea…

0

1 Like

Ok, strangely those were checked for me, even if I never want them and I know the the SDK missing is particularly used on OSX so maybe we’re getting closer.

They are checket by default.
I unchecket them becuase i don’t need them.
i hope it work for you!!

Ok, I unchecked those and installed the debugging symbols, but same problem with Rider while no problem with Windows.

Do not use the .sln file to open your project with Rider.
Use the .uproject instead.

14 Likes

It actually worked, opening the uproject instead of the sln. I would have never expected that.
Thank you!

3 Likes

You are wellcome!! :heart:

In my case, installing the right SDK in Visual Studio Setup and updating Rider helped.
Something like this:
VisualStudioSetup.exe → modify → components

Sorry about the screenshot =)

2 Likes

I tried to install the SDK you highlighted, and Rider is already updated, but without success. For now, loading the uproject is the working solution.
Thank you for the suggestion

I got the same issue after installing 5.3 and this fixed this error message for me too.
I also updated the SDK of .net and updated my MSVC to the latest version.
This is a very weird solution for the problem. Can you update here when you found a solution for using the .sln?

I think it is not possible… it is a Rider version than only works using uproject. But you can try changing the editor preferencies (I din’t tried it).

3 Likes

I actually just right clicked on the uproject and “Open with” Rider

1 Like