Visual Studio IDE Tracks VS Code Extension Model -- Visual Studio Magazine

Visual Studio IDE Tracks VS Code Extension Model

By David Ramel
03/27/2018

Microsoft's flagship Visual Studio IDE is continuing to track the extension model introduced with the company's lightweight, open source, cross-platform Visual Studio Code editor.

The latest move in that direction introduces support for debug adapters, which let Visual Studio developers implement debugging extensions they've previously written for VS Code, with a little tweaking.

One of the most popular features of VS Code is its extension model, allowing developers to add all kinds of functionality from its Marketplace. For example, its top five extensions have all been downloaded more than 6 million times, with the Python programming language extension topping the list at more than 8.2 million installs.

While the extension model was baked into VS Code from its beginning, Microsoft only began to introduce the model to Visual Studio IDE last November, with the release of the Language Server Protocol preview. Developed by Microsoft and hosted on GitHub, that protocol provides a standard way to provide language service features to code editors, such as IntelliSense, error diagnostics, find all references, auto complete, go to definition and so on.

**[Click on image for larger view.]** Debug Adapter Overview *(source: Microsoft).*

Yesterday (March 26), the Visual Studio Engineering Team announced the addition of support for debug adapters and explained how to start using them.

"Now, in Visual Studio 2017 version 15.6, we're excited to announce support for another Visual Studio Code extension component -- the debug adapter," said Andrew Crawley senior software engineer, Visual Studio, in a blog post.

"If you've previously written a debugging extension for Visual Studio Code, you can now use it in Visual Studio as well, generally with only minor modifications. If you're considering implementing debugging support for a language or runtime, doing so via a debug adapter will allow you to reach both Visual Studio and Visual Studio Code customers without having to support two separate codebases."

He said the Debug Adapter Protocol is JSON-based, providing libraries for using it with many languages including Node.JS and C#/VB.Net.

More information is available in the GitHub site for the Visual Studio Debug Adapter Host, the Debug Adapter Host wiki and documentation for adding a Language Server Protocol extension.

About the Author

David Ramel is an editor and writer at Converge 360.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.