-
Notifications
You must be signed in to change notification settings - Fork 759
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Visual Studio Support #551
Comments
First step towards this is #290 I think. |
For anyone interested in seeing this happen, please upvote the feature request on the VS tracker as well. |
+1 It's a horrible experience having to jump around different IDEs for different parts of my work, especially as part of the same pull request. |
Hey everyone! Thank you so much for keeping up with this thread. We can see Bicep in Visual Studio is very important to our customers and we are currently working on an Out-of-box extension to make this happen. The plan is that any and all Bicep Language Server features that can be supported within Visual Studio (colorization, tab completions) will be available to make authoring easier, but we do not yet have plans for certain features like the Bicep Visualizer or right click deploy. Right now we are working through the Visual Studio features set when it comes to its Language Server Protocol as not every feature capability is 1 to 1. Thank you for your patience and we are looking forward to bringing you a great Bicep in VS Experience! |
Is your feature request related to a problem? Please describe.
It would be great to be able to work on Bicep within Visual Studio, perhaps as part of an Azure Resource Group project.
Describe the solution you'd like
I'd like to see editor support for Bicep syntax in Visual Studio. It would also be really cool if there was a Toolbox in Visual studio which allowed a drag-and-drop of Azure resources onto the editor which generates the bicep code. Editing the fields of the resources in the properties window would be nice as well.
The text was updated successfully, but these errors were encountered: