News

Visual Studio Code Feedback Loop, First Updates

The Visual Studio Code Team improves a few features of the portable code editor -- in particular, public issue tracking and centralized feedback channnel -- while still in preview.

Visual Studio Code, the new portable code editor from Microsoft that was revealed during the Build conference a few weeks ago in San Francisco, already has some important tooling updates while in preview. Much of the work for these updates are a result, of course, of feedback from early adopters, according to the company.

"Within the first week it became clear that there were a number of common issues people were running into," said Sean McBreen, a Visual Studio Code Team Member, in a blog post last week. A number of issues are being addressed in a FAQ document the team has published online. The first few issues, naturally, have to do with installation and uninstalling Visual Studio Code, while others have to do with debugging and keyboarding.

The FAQ is a direct result of a project the Visual Studio Online Team had worked on that's aimed at improving the shortcomings of the current feedback channel. Microsoft's Brian Harry wrote about that project in a separate, related blog post, detailing the frustration of the Visual Studio Code team with the current process. "Microsoft Connect just isn't a pleasant experience," he wrote. "They looked at UserVoice and it's great for suggestions but not optimized for bugs."

The team ran a hackathon that, at the end of three days, produced an issues portal that itself runs on Visual Studio Online. Harry explains that it's brand new, and what they plan to do with it in the future -- open source it, expand its portability -- really depends on developer feedback from the community.

Issues can also be channeled through the Connect Web site and UserVoice, as usual. To stay up-to-date on Visual Studio Code, developers can sign up to the Insider program by first filling out a survey.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

comments powered by Disqus

Featured

  • Copilot AI Billing Shock Met with Meters, Caps and Token-Saving Tools

    GitHub is layering spending limits, expanded credit allowances and increasingly granular usage reporting onto Copilot, while Microsoft is reworking Visual Studio and VS Code to expose -- and reduce -- the cost of agentic development.

  • The AI-Powered Software Development Lifecycle

    René van Osnabrugge makes the case that AI's biggest opportunity in software development is not faster coding -- it's reducing the friction everywhere else in the SDLC.

  • Copilot Usage-Based Billing Gets a Token Dashboard

    Microsoft is keeping Visual Studio's new built-in Agent Skills switched off by default while a public dashboard measures whether their performance gains justify the additional tokens they may consume.

  • VS Code 1.129 Introduces Agent Host and Experimental Agents Window Editor

    Visual Studio Code 1.129 adds a dedicated process for running AI agent sessions and an experimental docked editor for reviewing agent-generated changes.

Subscribe on YouTube