dotnet-core/release-notes/6.0/known-issues.md

.NET 6.0 Known Issues

You may encounter the following known issues, which may include workarounds, mitigations or expected resolution timeframes.

.NET SDK

1. WPF App may fail to build or publish

Publish in Visual Studio

When publishing a WPF project in Visual Studio with a target runtime specified, the publish operation may fail and display a message similar to the following in the output window:

Assets file ‘c:\git\repro\WPFSelfContained\obj\project.assets.json’ doesn’t have a target for ‘net5.0-windows/win-x64’. Ensure that restore has run and that you have included ‘net5.0-windows’ in the TargetFrameworks for your project. You may also need to include ‘win-x64’ in your project’s RuntimeIdentifiers.

Customized output paths

When building a project that redirects the intermediate and/or output paths to a folder using the MSBuildProjectName MSBuild property, for example via the following in a Directory.Build.props file:

<PropertyGroup>
    <RepoRoot>$([System.IO.Path]::GetFullPath('$(MSBuildThisFileDirectory)'))</RepoRoot>
    <BaseOutputPath>$(RepoRoot)artifacts\bin\$(MSBuildProjectName)\</BaseOutputPath>
    <BaseIntermediateOutputPath>$(RepoRoot)artifacts\obj\$(MSBuildProjectName)\</BaseIntermediateOutputPath>
  </PropertyGroup>

An error similar to the following may be generated:

error NETSDK1004: Assets file ‘c:\git\repro\wpf\artifacts\obj\wpf_gzmmtwnk_wpftmp\project.assets.json’ not found. Run a NuGet package restore to generate this file.

Workaround

You can workaround these issues by setting the IncludePackageReferencesDuringMarkupCompilation property to false in the project file:

<PropertyGroup> <IncludePackageReferencesDuringMarkupCompilation>false</IncludePackageReferencesDuringMarkupCompilation> </PropertyGroup>

Windows Forms

• PropertyGrid values are rendered at incorrect location.

  The issue is tracked in dotnet/winforms#4593 and is expected to be fixed in 6.0 Preview3.