News

What's New in Visual Studio Code January 2019 Release

The latest monthly release (January 2019, version 1.31) of the cross-platform Visual Studio Code editor comes with the usual plethora of bug fixes, tweaks and new features, with many focused on the extension mechanism that powers the open source project.

These extensions come from many sources ranging from individual developers to corporate dev teams, with several popular offerings on the Visual Studio Code Marketplace having been downloaded tens of millions of times.

The January update includes several extension-related initiatives including:

  • Updated Extension API documentation that has been completely rewritten with extension guides.
  • Extension authoring changes including: a new change event; the ability to open resources in a browser; a new global storage path -- ExtensionContext.globalStoragePath -- that points to a local directory with write/read access; and more.
  • The ability to install extensions without forcing a reload or restart of VS Code.
  • Network proxy support for extensions such that the setting Http: Proxy Support (http.proxySupport) now enables network proxy support for all extensions by default.
  • All extensions will run on an updated version of the Electron platform that powers VS Code, which comes with update from Node.js 8.9 to v10.2.0.
Updated Extension API documentation
[Click on image for larger view.] Updated Extension API Documentation (source: Microsoft).

Regarding the Extension API, Microsoft said it rewrote its documentation and moved it to its own table of contents. The documentation includes articles to:

The January milestone, like all others, also includes proposed extension APIs that extension authors can try out, provided they:

  • Participate in the Insiders program (early access to new builds) because proposed APIs change frequently.
  • Have this line in the package.json file of an extension: "enableProposedApi": true.
  • Copy the latest version of the vscode.proposed.d.ts file into a project.

"Note that you cannot publish an extension that uses a proposed API," the dev team said in a blog post today (Feb. 6). "We may likely make breaking changes in the next release and we never want to break existing extensions."

Among a bevy of other new features and bug fixes, the dev team especially highlighted the following:

Furthermore, the team categorized some new stuff according to related VS Code focus areas:

  • Workbench -- Zen Mode hides line numbers, new Screencast mode shows keystrokes.
  • Editor -- Smart selection improvements, tune Reference CodeLens location.
  • Integrated Terminal -- ConPTY support on Windows, Find improvements.

Visual Studio Code source code is listed on GitHub, where the project shows 68,552 stars and 814 contributors.

About the Author

David Ramel is an editor and writer at Converge 360.

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.

Subscribe on YouTube