diff options
| author | Rahul Bhandari <rbhanda@microsoft.com> | 2021-08-12 20:39:44 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-08-12 20:39:44 +0300 |
| commit | 394bbaf4029bc5ef3c1740bfc30d17a8179bb62b (patch) | |
| tree | 9a8f77508377f89e3cf96faf027c2191ec536a8a | |
| parent | acd28d65d2d129fc61a139d2baa8e9e5a7b7718e (diff) | |
| parent | b87a8b38cb6d4ac73c3114ff3b088b1377d599a8 (diff) | |
Merge pull request #6576 from dotnet/marcpopMSFT-AddWorkloadGCWorkaroundv2.1.29
Add GC workaround per customer feedback
| -rw-r--r-- | release-notes/6.0/known-issues.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/release-notes/6.0/known-issues.md b/release-notes/6.0/known-issues.md index 221bcb38..ca254a8f 100644 --- a/release-notes/6.0/known-issues.md +++ b/release-notes/6.0/known-issues.md @@ -17,6 +17,15 @@ The workload names all changed between preview 6 and 7 so the SDK doesn't recogn `Garbage collecting for SDK feature bands 6.0.100... Workload installation failed: Workload not found: microsoft-net-sdk-blazorwebassembly-aot. Known workloads: ...` +Another potential error +`Garbage collecting for SDK feature bands 6.0.100… +Workload installation failed: The JSON value could not be converted to Microsoft.NET.Sdk.WorkloadManifestReader.WorkloadPackId. Path: $.Id | LineNumber: 0 | BytePositionInLine: 40.` + +**Workaround** +Delete your dotnet\metadata folder and try the workload install again. The metadata folder contains our records of what workloads you've tried to install and is what's triggering us to try to clean up an older workload that may not be recognized or compatible with the current SDK. + +Note that a side effect of this is that the SDK will leave behind some older preview workloads across various _packs_ directories. + ### Preview 5 #### 1. Missing Workload Manifests in Visual Studio 17 Preview 1 |