Skip to content

Commit a664fa4

Browse files
Merge pull request #217058 from mumian/1103-vs-integration
Mention Visual Studio Code in article
2 parents 245ed07 + 3703460 commit a664fa4

File tree

5 files changed

+21
-5
lines changed

5 files changed

+21
-5
lines changed

articles/azure-resource-manager/bicep/install.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Set up Bicep development and deployment environments
33
description: How to configure Bicep development and deployment environments
44
ms.topic: conceptual
5-
ms.date: 08/08/2022
5+
ms.date: 11/03/2022
66
ms.custom: devx-track-azurepowershell, devx-track-azurecli
77
---
88

@@ -13,6 +13,7 @@ Let's make sure your environment is set up for working with Bicep files. To auth
1313
| Tasks | Options | Bicep CLI installation |
1414
| ------ | ------- | ----------- |
1515
| Author | [VS Code and Bicep extension](#vs-code-and-bicep-extension) | automatic |
16+
| | [Visual Studio and Bicep extension](#visual-studio-and-bicep-extension) | automatic |
1617
| Deploy | [Azure CLI](#azure-cli) | automatic |
1718
| | [Azure PowerShell](#azure-powershell) | [manual](#install-manually) |
1819
| | [VS Code and Bicep extension](#vs-code-and-bicep-extension) | automatic |
@@ -39,6 +40,15 @@ If you get an error during installation, see [Troubleshoot Bicep installation](i
3940

4041
You can deploy your Bicep files directly from the VS Code editor. For more information, see [Deploy Bicep files from Visual Studio Code](deploy-vscode.md).
4142

43+
## Visual Studio and Bicep extension
44+
45+
To author Bicep file from Visual Studio, you need:
46+
47+
- **Visual Studio** - If you don't already have Visual Studio, [install it](https://visualstudio.microsoft.com/).
48+
- **Bicep extension for Visual Studio**. Visual Studio with the Bicep extension provides language support and resource autocompletion. The extension helps you create and validate Bicep files. Install the extension from [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
49+
50+
To walk through a tutorial, see [Quickstart: Create Bicep files with Visual Studio](./quickstart-create-bicep-use-visual-studio.md).
51+
4252
## Azure CLI
4353

4454
When you use Azure CLI with Bicep, you have everything you need to [deploy](deploy-cli.md) and [decompile](decompile.md) Bicep files. Azure CLI automatically installs the Bicep CLI when a command is executed that needs it.

articles/azure-resource-manager/bicep/overview.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Bicep language for deploying Azure resources
33
description: Describes the Bicep language for deploying infrastructure to Azure. It provides an improved authoring experience over using JSON to develop templates.
44
ms.topic: conceptual
5-
ms.date: 03/14/2022
5+
ms.date: 11/03/2022
66
---
77

88
# What is Bicep?
@@ -76,9 +76,11 @@ Bicep provides the following advantages:
7676
---
7777

7878
- **Authoring experience**: When you use the [Bicep Extension for VS Code](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep) to create your Bicep files, you get a first-class authoring experience. The editor provides rich type-safety, intellisense, and syntax validation.
79-
79+
8080
![Bicep file authoring example](./media/overview/bicep-intellisense.gif)
8181

82+
You can also create Bicep files in Visual Studio with the [Bicep extension for Visual Studio](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
83+
8284
- **Repeatable results**: Repeatedly deploy your infrastructure throughout the development lifecycle and have confidence your resources are deployed in a consistent manner. Bicep files are idempotent, which means you can deploy the same file many times and get the same resource types in the same state. You can develop one file that represents the desired state, rather than developing lots of separate files to represent updates.
8385
- **Orchestration**: You don't have to worry about the complexities of ordering operations. Resource Manager orchestrates the deployment of interdependent resources so they're created in the correct order. When possible, Resource Manager deploys resources in parallel so your deployments finish faster than serial deployments. You deploy the file through one command, rather than through multiple imperative commands.
8486

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

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create Bicep files - Visual Studio Code
33
description: Use Visual Studio Code and the Bicep extension to Bicep files for deploy Azure resources
4-
ms.date: 06/30/2022
4+
ms.date: 11/03/2022
55
ms.topic: quickstart
66
ms.custom: devx-track-azurepowershell, mode-ui
77
#Customer intent: As a developer new to Azure deployment, I want to learn how to use Visual Studio Code to create and edit Bicep files, so I can use them to deploy Azure resources.
@@ -11,6 +11,8 @@ ms.custom: devx-track-azurepowershell, mode-ui
1111

1212
This quickstart guides you through the steps to create a [Bicep file](overview.md) with Visual Studio Code. You'll create a storage account and a virtual network. You'll also learn how the Bicep extension simplifies development by providing type safety, syntax validation, and autocompletion.
1313

14+
Similar authoring experience is also supported in Visual Studio. See [Quickstart: Create Bicep files with Visual Studio](./quickstart-create-bicep-use-visual-studio.md).
15+
1416
## Prerequisites
1517

1618
If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.

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

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ ms.topic: quickstart
1111

1212
This quickstart guides you through the steps to create a [Bicep file](overview.md) with Visual Studio. You'll create a storage account and a virtual network. You'll also learn how the Bicep extension simplifies development by providing type safety, syntax validation, and autocompletion.
1313

14+
Similar authoring experience is also supported in Visual Studio Code. See [Quickstart: Create Bicep files with Visual Studio Code](./quickstart-create-bicep-use-visual-studio-code.md).
15+
1416
## Prerequisites
1517

1618
- Azure Subscription. If you don't have an Azure subscription, [create a free account](https://azure.microsoft.com/free/) before you begin.

articles/azure-resource-manager/bicep/quickstart-private-module-registry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ To work with module registries, you must have [Bicep CLI](./install.md) version
1919

2020
A Bicep registry is hosted on [Azure Container Registry (ACR)](../../container-registry/container-registry-intro.md). To create one, see [Quickstart: Create a container registry by using a Bicep file](../../container-registry/container-registry-get-started-bicep.md).
2121

22-
To set up your environment for Bicep development, see [Install Bicep tools](install.md). After completing those steps, you'll have [Visual Studio Code](https://code.visualstudio.com/) and the [Bicep extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep).
22+
To set up your environment for Bicep development, see [Install Bicep tools](install.md). After completing those steps, you'll have [Visual Studio Code](https://code.visualstudio.com/) and the [Bicep extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-bicep), or [Visual Studio](https://visualstudio.microsoft.com/) and the [Bicep extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.visualstudiobicep).
2323

2424
## Create Bicep modules
2525

0 commit comments

Comments
 (0)