diff options
| author | Rahul Bhandari <rbhanda@microsoft.com> | 2022-07-12 01:01:13 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-12 01:01:13 +0300 |
| commit | 4bf75eeefb32955453ddbf9fb65c48b70db2e886 (patch) | |
| tree | f08152f27794625381996180fac3e60c0ddea433 | |
| parent | 65d3fc6f575a8a5b7207bb9f14a13cb8151298a3 (diff) | |
Update release-notes/7.0/known-issues.md
Co-authored-by: Marc Paine <marcpop@microsoft.com>
| -rw-r--r-- | release-notes/7.0/known-issues.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/release-notes/7.0/known-issues.md b/release-notes/7.0/known-issues.md index 1d8f51e3..7a1c8fdf 100644 --- a/release-notes/7.0/known-issues.md +++ b/release-notes/7.0/known-issues.md @@ -61,7 +61,7 @@ Workaround: Setting DOTNET_ROOT to point to the path to the local dotnet fixes t ### Blazor issues depending on whether you’re using .NET 6 installed by VS or stand-alone install of .NET 7 -If your app is targetting Blazor using the .net 7 included in VS, you can target net6.0 but not target net7.0 and you will see an error message 'The "ProcessFrameworkReferences" task faield unexpectedly.' +If your app is targetting Blazor using the .net 7 included in VS, you can target net6.0 but not target net7.0 and you will see an error message 'The "ProcessFrameworkReferences" task faield unexpectedly.' Workaround: |