Skip to content

Commit 3033b3e

Browse files
authored
Merge pull request #281258 from mumian/0718-problem-pane
Cover vscode problems pane
2 parents 45e803a + a99b108 commit 3033b3e

File tree

2 files changed

+10
-2
lines changed

2 files changed

+10
-2
lines changed
35.9 KB
Loading

articles/azure-resource-manager/bicep/visual-studio-code.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create Bicep files by using Visual Studio Code
33
description: Describes how to create Bicep files by using Visual Studio Code
44
ms.topic: how-to
55
ms.custom: devx-track-bicep
6-
ms.date: 05/10/2024
6+
ms.date: 07/18/2024
77
---
88

99
# Create Bicep files by using Visual Studio Code
@@ -127,7 +127,7 @@ From Visual Studio Code, you can open the template reference for the resource ty
127127

128128
## Go to definition
129129

130-
When defining a [module](./modules.md), regardless of the types of the referenced file - whether it is a local file, module registry file, template spec, you can open the referenced file by selecting or highlighting the module path and then press **[F12]**. If the referenced file is an [Azure Verified Modules(AVM)](https://aka.ms/avm), you can toggle between compiled JSON or Bicep file. To be able to open the Bicep file of a private registry module, ensure that the module is published to the registry with the `WithSource` switch enabled. For more information, see [Publish files to registry](./private-module-registry.md#publish-files-to-registry). The Visual Studio Code Bicep extension version 0.27.1 or newer is required for opening Bicep file from private module registry.
130+
When defining a [module](./modules.md), regardless of the types of the referenced file - whether it's a local file, module registry file, template spec, you can open the referenced file by selecting or highlighting the module path and then press **[F12]**. If the referenced file is an [Azure Verified Modules(AVM)](https://aka.ms/avm), you can toggle between compiled JSON or Bicep file. To be able to open the Bicep file of a private registry module, ensure that the module is published to the registry with the `WithSource` switch enabled. For more information, see [Publish files to registry](./private-module-registry.md#publish-files-to-registry). The Visual Studio Code Bicep extension version 0.27.1 or newer is required for opening Bicep file from private module registry.
131131

132132
## Paste as Bicep
133133

@@ -195,6 +195,14 @@ Visual Studio Code automatically converts the JSON to Bicep. Notice that you als
195195

196196
You can undo the decompilation by using <kbd>Ctrl+Z</kbd>. The original JSON appears in the file.
197197

198+
## Troubleshoot
199+
200+
The `Problems` pane summarizes the errors and warning in your Bicep file.
201+
202+
:::image type="content" source="./media/visual-studio-code/visual-studio-code-bicep-problems-pane.png" alt-text="Screenshot of Visual Studio Code Bicep problems pane.":::
203+
204+
For the list of error/warning codes, see [Bicep error/warning codes](./bicep-error-codes.md).
205+
198206
## Next steps
199207

200208
To walk through a quickstart, see [Quickstart: Create Bicep files with Visual Studio Code](./quickstart-create-bicep-use-visual-studio-code.md).

0 commit comments

Comments
 (0)