.NET 6 RC1

[kalaskarsanket]

Release Notes

Please report any issues you find with .NET 6, either responding to this issue, creating a new issue or creating a new issue in one of the following repos:

• dotnet/aspnetcore - for ASP.NET Core questions
• dotnet/efcore - for Entity Framework Core questions
• dotnet/sdk - for CLI tools and questions
• dotnet/runtime - for runtime, API, or installer issues and questions
• dotnet/winforms - for WinForms issues
• dotnet/wpf - for WPF issues
• nuget/home - for NuGet questions and issues

Important thing note is that this issue impacted VS Hot Reload scenarios only. Users who experienced this issue should update to the latest VS.

Known Issues

If there are any issues with this release we will track them here and check issues off as they're resolved. See the linked issues for details on progress and resolution details.

Update

During the hot reload compilation, tag helpers from references were not being resolved which resulted in component tags being treated as plain html. The fix for this issue has been made to the Razor Source Generator. As a result we have updated the .NET 6 RC1 SDK to 6.0.100-rc.1.21463.6.

[jonathanpeppers]

I think they renamed @(Import) to @(Using), you might try:

<ItemGroup>
  <Using Remove="System.Net.Http" />
</ItemGroup>

[yamachu]

Although it is not directly related to core, I could not find the Feedback destination, so I will write it here.

I noticed when I downloaded rc.1, is the Latest release date intended?

https://dotnet.microsoft.com/download/dotnet/6.0

[kalaskarsanket]

@yamachu Thanks for letting us know, we are working on the date issue and should be corrected soon.

[MarcelMichau]

Hi there!

Not sure exactly where to post this, as it's more related to Azure App Service than .NET 6 specifically, but could anyone provide some information/timelines on when the .NET 6 RC1 runtime might be rolled out to App Service?

It seems like the App Service instances are still on Preview 7 at the moment, at least in the North Europe region.

Thanks very much!

[teo-tsirpanis]

Installing RC 1 removes Preview 7 from the installed programs list, but not the actual files. When I installed Preview 7 again, it completed very quickly, indicating that nothing was done. When I tried to remove it manually, it completed very quickly again, and the files remained.

[AroglDarthu]

We've ran into a similar problem as the one described here: dotnet/msbuild#6389

Unhandled exception: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
   ---> System.PlatformNotSupportedException: Strong-name signing is not supported on this platform.
     at System.Reflection.AssemblyName.get_KeyPair()

Although https://github/dotnet/msbuild/issues is not in your list above, I am wondering if these are related. Does it need a separate fix in any of the other repos, or do we just have to be patient and wait for a future net6.0-rc?

[murbanowicz]

The snap version which is recommended to be used on Linux for preview/rc is still broken for this version.
It is impossible to install .NET 6 without the pain on Linux at the moment.
On Fedora we are hitting: cannot snap-exec: cannot exec "/var/lib/snapd/snap/dotnet-sdk/142/snap/command-chain/snapcraft-runner": permission denied for whole .NET 6 release chain since few months.
I still cannot get why Windows and Mac get installers for previews/rc, but Linux distros don't get them in package managers.

[leXorNet]

Hi,
While plain net6.0 (rc1) works fine for me, I'm having real issues when adding the MacOS workload.
Build times for a simple "hello world" goes from ~1 sec to ~10 sec and breakpoints stop working (VS-Mac 2019).

Also, I can't get a two project setup to work (console-project that depends on a lib-project), when one or both is targeting macos. A sample solution for this would be appreciated :) Please see error below.

Projects:

<TargetFramework>net6.0-macos</TargetFramework>
<RuntimeIdentifier>osx-x64</RuntimeIdentifier>

Error:
"/usr/local/share/dotnet/packs/Microsoft.NET.Runtime.MonoTargets.Sdk/6.0.0-rc.1.21451.13/Sdk/RuntimeComponentManifest.targets(3,5): error : Empty ResolveFrameworkReference.RuntimePackPath while trying to read runtime components manifest. ResolvedFrameworkReference available: { Microsoft.NETCore.App, RuntimePackPath: }"

[rbhanda]

closing in favor of #6795

[AlexeyStarkov]

Hi, While plain net6.0 (rc1) works fine for me, I'm having real issues when adding the MacOS workload. Build times for a simple "hello world" goes from ~1 sec to ~10 sec and breakpoints stop working (VS-Mac 2019).

Also, I can't get a two project setup to work (console-project that depends on a lib-project), when one or both is targeting macos. A sample solution for this would be appreciated :) Please see error below.

Projects:

<TargetFramework>net6.0-macos</TargetFramework>
<RuntimeIdentifier>osx-x64</RuntimeIdentifier>

Error: "/usr/local/share/dotnet/packs/Microsoft.NET.Runtime.MonoTargets.Sdk/6.0.0-rc.1.21451.13/Sdk/RuntimeComponentManifest.targets(3,5): error : Empty ResolveFrameworkReference.RuntimePackPath while trying to read runtime components manifest. ResolvedFrameworkReference available: { Microsoft.NETCore.App, RuntimePackPath: }"

Did you solve that "Empty ResolveFrameworkReference.RuntimePackPath" problem? I'm facing the same issue with MAUI and "net7.0-ios" target framework

[jongfeel]

Hi, While plain net6.0 (rc1) works fine for me, I'm having real issues when adding the MacOS workload. Build times for a simple "hello world" goes from ~1 sec to ~10 sec and breakpoints stop working (VS-Mac 2019).
Also, I can't get a two project setup to work (console-project that depends on a lib-project), when one or both is targeting macos. A sample solution for this would be appreciated :) Please see error below.
Projects:

<TargetFramework>net6.0-macos</TargetFramework>
<RuntimeIdentifier>osx-x64</RuntimeIdentifier>

Error: "/usr/local/share/dotnet/packs/Microsoft.NET.Runtime.MonoTargets.Sdk/6.0.0-rc.1.21451.13/Sdk/RuntimeComponentManifest.targets(3,5): error : Empty ResolveFrameworkReference.RuntimePackPath while trying to read runtime components manifest. ResolvedFrameworkReference available: { Microsoft.NETCore.App, RuntimePackPath: }"

Did you solve that "Empty ResolveFrameworkReference.RuntimePackPath" problem? I'm facing the same issue with MAUI and "net7.0-ios" target framework

@leXorNet
@AlexeyStarkov

Hi guys, I've got same issue with MAUI and xUnit project on MacOS.

and I've fix this problem and hope this link help.

https://cedricgabrang.medium.com/adding-xunit-test-to-your-net-maui-project-ee36c00a8542