Net6 Rider EAP Cant even resolve "System"

Wanting to have a look at the hot reloading stuff in .net6 in linux as I have a project that could benefit from it.

I installed the .net6 SDK,

got the Rider EAP8,

Tried targeting .net6 in the existing project and had errors *everywhere* and it couldn't even resolve "using System".

Tried creating a new console app targeting .net6 and same result.

am I being dumb and doing something wrong, or is there a known issue with EAP8?

6 comments
Comment actions Permalink

I can build the project from the cli, and even get hotreload working using dotnet watch.

Rider is still struggling to resolve librarys though.

if I try to build in rider I get this message:

Microsoft.Common.CurrentVersion.targets(1193, 5): [MSB3644] The reference assemblies for .NETFramework,Version=v6.0 were not found. To resolve this, install the Developer Pack (SDK/Targeting Pack) for this framework version or retarget your application. You can download .NET Framework Developer Packs at https://aka.ms/msbuild/developerpacks

Yet as I stated previously, it builds fine with dotnet build.

0
Comment actions Permalink

Found that Use MSBuild setting was pointing to mono, not .net6

(File->Settings->Toolset and Build)

0
Comment actions Permalink

Hi se5a

Sorry for the delay. Did changing the toolset solve the problem? 

0
Comment actions Permalink

Yes it did, thankyou.

Might it be possible for rider to provide a hint as to this being the problem? I suspect at least one other issue in this forum is caused by this.

0
Comment actions Permalink

se5a in most cases the right ms-build should be selected by autodetecting.  Could you please check if mono is marked as auto-detected in `File->Settings->Toolset and Build`? If it is, can we ask you for some logs for investigating the issue? 

As to hint, there is a Problems View with indications of MSBuild problems on the `Toolset, Environment` tab. 

0
Comment actions Permalink

Ah, I hadn't seen the `Toolset, Environment` tab. yes the hint there might have helped me find the problem a bit quicker.

The .net6 version is marked as autodetected.

Maybe I had set it to the one in mono for some reason previously? it was set globally rather than just for this project since I was having the same problem when I created a new solution and project.(and I've now set it to the autodetect option globally).

 

0

Please sign in to leave a comment.