Skip to content

Commit 6d4da8e

Browse files
committed
update
1 parent b9ce5b9 commit 6d4da8e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-resource-manager/bicep/installation-troubleshoot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -73,10 +73,10 @@ From VSCode, open the **Output** view in the pane at the bottom of the screen, a
7373

7474
:::image type="content" source="./media/installation-troubleshoot/visual-studio-code-output-pane-bicep.png" alt-text="Visual Studio Code output pane":::
7575

76-
If you see the following output in the pane, and you are using Bicep CLI v0.4.1124 or later, check whether you have added the `dotnetAcquisitionExtension.existingDotnetPath` configuration option to VSCode. See [.NET runtime error](#net-runtime-error). If this configuration option is present, remove it and restart VSCode.
76+
If you see the following output in the pane, and you are using Bicep CLI **version 0.4.1124** or later, check whether you have added the `dotnetAcquisitionExtension.existingDotnetPath` configuration option to VSCode. See [.NET runtime error](#net-runtime-error). If this configuration option is present, remove it and restart VSCode.
7777

7878
```error
79-
It was not possible to find any compatible framework version
79+
It was not possible to find any compatible framework version.
8080
```
8181

8282
Otherwise, raise an issue in the [Bicep repo](https://github.com/Azure/bicep/issues), and include the output messages.

0 commit comments

Comments
 (0)