Update known-issues.md

dotnet · Oct 12, 2021 · 9e60840 · 9e60840
1 parent 50dc527
commit 9e60840
Showing 1 changed file with 21 additions and 0 deletions.
diff --git a/release-notes/6.0/known-issues.md b/release-notes/6.0/known-issues.md
@@ -16,6 +16,27 @@ If you build .NET 6 projects with MSBuild 16.11, for example, you will see the f
 Installing MSI based optional workloads using the CLI will result in a `PlatformNotSupported` exception on Windows (arm64). The CLI installer has a dependency on `System.Management` that is not support on Windows (arm64). This dependency has been removed in RC2.
 
 There is no workaround for this issue in RC1, except to switch to the file based workload installation.
+
+#### 2. Reference assemblies no longer output to the bin directory
+
+These files are only needed during builds and cause confusion for customers to see extra binaries built to the bin\ref folder. Instead they were [moved](https://github.com/dotnet/msbuild/pull/6560) to only build to the obj/ref folder.
+
+**Note, this change is being [reverted](https://github.com/dotnet/msbuild/pull/6718) for RC1 as we found a hardcoded path in Roslyn in VS scenarios that has to be addressed first**
+
+#### 3. Workload install for protected install location (eg. c:\program files) will fail
+
+In the future, the .NET SDK will trigger elevation to install missing workloads but today that fails.
+
+```
+C:\Users\MPP>dotnet workload install microsoft-macos-sdk-full --skip-manifest-update
+
+Installing pack Microsoft.macOS.Sdk version 11.3.100-preview.5.889...
+Workload installation failed, rolling back installed packs...
+Rolling back pack Microsoft.macOS.Sdk installation...
+Workload installation failed: One or more errors occurred. (Access to the path 'C:\Program Files\dotnet\metadata\temp\microsoft.macos.sdk\11.3.100-preview.5.889' is denied.)
+```
+**Workaround**
+You'll need to elevate your command prompt before running the install command.
 
 ## ASP.NET Core