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

37 lines
1.8 KiB
Markdown
Raw Normal View History

2021-02-17 17:31:48 +01:00
# .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 doesnt 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 projects 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:
```xml
<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>`