Skip to content

Commit 36b3d57

Browse files
committed
update
1 parent f5829f5 commit 36b3d57

1 file changed

Lines changed: 13 additions & 1 deletion

File tree

articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md

Lines changed: 13 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create Bicep files - Visual Studio
33
description: Use Visual Studio and the Bicep extension to create Bicep files for deploy Azure resources.
4-
ms.date: 12/22/2025
4+
ms.date: 01/13/2026
55
ms.topic: quickstart
66
ms.custom: devx-track-bicep
77
#Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio to create and edit Bicep files, so I can use them to deploy Azure resources.
@@ -20,6 +20,18 @@ Similar authoring experience is also supported in Visual Studio Code. See [Quick
2020
- Visual Studio Bicep extension. See [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
2121
- Bicep file deployment requires either the latest [Azure CLI](/cli/azure/) or the latest [Azure PowerShell module](/powershell/azure/new-azureps-module-az).
2222

23+
> [!INFO]
24+
> To make all diagnostics generated by Bicep (Errors, Warnings, and Informational messages) are correctly surfaced as native MSBuild diagnostics, configure `BicepTreatInfoAsWarnings` in your project file. For example:
25+
>
26+
> ```xml
27+
><Project Sdk="Microsoft.Build.NoTargets">
28+
> <PropertyGroup>
29+
> <TargetFramework>net472</TargetFramework>
30+
> <BicepTreatInfoAsWarnings>true</BicepTreatInfoAsWarnings>
31+
> </PropertyGroup>
32+
></Project>
33+
> ```
34+
2335
## Add resource snippet
2436
2537
Launch Visual Studio and create a new file named **main.bicep**.

0 commit comments

Comments
 (0)