News

After Last 2020 VS Code Update, What's In Store for 2021?

With the year's last release of Visual Studio Code out in a "housekeeping" update, Microsoft highlighted new features and pointed to what's to come in 2021 for its popular open source cross-platform code editor.

Even though VS Code v1.52 (November 2020 update) saw the dev team devoted to cleaning up end-of-year housekeeping chores for two weeks, an announcement post did highlight new features and settings, with the top 10 being:

If you wondered what's involved with VS Code housekeeping, Microsoft said, "Across all of our VS Code repositories, we closed (either triaged or fixed) 5242 issues, which is even more than during our last housekeeping iteration in October 2019, where we closed 4622 issues. While we closed issues, you created 2937 new issues. The main vscode repository now has 2146 open feature requests and 884 open bugs. In addition, we closed 144 pull requests."

When you start a code navigation (for example, with Go to Definition), the editor you start from will move out of preview mode and stay open, while the new editor will be in preview mode until you navigate further.
[Click on image for larger, animated GIF view.]See in Action: "When you start a code navigation (for example, with Go to Definition), the editor you start from will move out of preview mode and stay open, while the new editor will be in preview mode until you navigate further." (source: Microsoft).

Going forward, the draft iteration plan for December 2020/January 2021 shows dozens of items ranging from accessibility to engineering in various stages ranging from "work in progress" to "under discussion within the team."

Here are some items marked "work in progress" (🏃) or "stretch goal for this iteration" (💪):

  • Accessibility
    • 🏃 Assess notebook accessibility #111255
  • Workbench
    • 🏃 Explore the concept of Trusted Workspaces #106488
    • 🏃 💪 Investigate predefined file filters search #106790
    • 🏃 💪 Explore support for adding/organizing imports on Paste #30066
    • 🏃 Improve the welcome pages #106715
    • 💪 Explore showing file decorations in editor tabs #49382
    • 🏃 Supporting to customize the product icons #92791
  • Notebook Editor
  • Languages
  • Debug

Many more such items can be found in other categories including testing, terminal, extensions and so on.

"This plan captures our work in late December and January," says the iteration plan on GitHub. "This is a 6-week iteration. We will ship in early February.

"Note: Our last Insider build of 2020 will go out on December 22. The first Insider build of 2021 will go out on January 5. Our team will have minimal presence between December 19 and January 3. Expect slow or no responses in this time frame. Thank you for your support and contributions in 2020! Happy Holidays to all of you."

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