Azure / Azure/bicep

Support Bicep extension in vscode.dev and github.dev

Open
#5,032 1 comment 3 reactions 0 assignees View on GitHub
enhancement investigate
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 2h
Merged PRs (30d)
79

Description

The Bicep extension depends on dotnet installed locally, and doesn't work in the VSCode web editor.

We should be able to get this working with Blazor's WASM support.

Related investigations:
https://github.com/OmniSharp/csharp-language-server-protocol/issues/456
https://github.com/dotnet/aspnetcore/issues/37732

Web Extension authoring guide:
https://code.visualstudio.com/api/extension-guides/web-extensions

Contributor guide

Open the contributing guide

Research direction

Start by reading the Web Extension authoring guide and inspect how the Bicep extension depends on locally installed dotnet. Review the linked language-server and ASP.NET Core investigations to understand the Blazor WASM path. Done means the Bicep extension works in both vscode.dev and github.dev without a local dotnet installation.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode, wasm
Domain
devtools, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.