Visual Studio Blog
The official source of product insight from the Visual Studio Engineering Team
Latest posts
AI Is Changing How We Code. It’s Also Changing How We Learn.
AI is changing software development at a pace no one can ignore. Developers now have powerful AI tools that can help us write code, understand unfamiliar codebases, troubleshoot problems, learn new frameworks, and get answers in seconds. That is an incredible opportunity. But as these tools become more capable, I believe something else is becoming more valuable too: learning directly from other developers. That’s one of the reasons I continue to believe so strongly in events like VSLive!. Learn from people who have done the work One of the things I value most about VSLive! is its focus on practica...
Today I will… improve test coverage
Today I want to look at how we can improve on the test coverage that we have in the Interview Coach application. This application has some unit tests in it already, but I'm sure there is room for improvement. Defining our baseline Before we start writing tests, it's a good idea to have a baseline of what our coverage is so that we can find out where the gaps are, rather than just writing tests "for the sake of writing tests". We can do this using the Analyze Code Coverage for All Tests, from either the Command Palette (CTRL + SHIFT + P) or the Tests menu. Running the analyzer, we can see where our coverage ...
Today I will… find hidden latency across a distributed .NET application
When a distributed application feels slow, the user sees one delay. The code behind that delay may run across a web frontend, backend services, databases, and external APIs. If you profile only the frontend while the backend is slow, the profiler can show that the frontend is healthy without revealing the actual bottleneck. This article shows how to narrow a cross-process performance problem with Visual Studio: identify the process that owns the slow operation, capture its CPU activity, inspect the report, and add a focused measurement when CPU samples cannot explain elapsed time. GitHub Copilot Profiler Agent...
Stop alt-tabbing into the wrong Visual Studio
A user asked for per-solution color themes. It already ships, and it goes further than they asked. You run several instances of Visual Studio side by side, one per solution, and they all look identical. Same taskbar icon, same alt-tab thumbnail, same chrome. So, you land in the wrong one, start typing, and realize thirty seconds later you just edited the wrong repo. Could each solution get its own color theme? It can. It already does. And the way it works turns out to be more useful than a personal color preference. How to do it This uses the new settings experience introduced in Visua...
Today I will… review GitHub PRs
Today I will show you how we can tackle one of the most common tasks when working in a development team or managing an open-source project, and that is working with Pull Requests. While we're going to be using the GitHub tooling within Visual Studio for this, the approach would be very similar with Azure DevOps. Getting our PRs Start by opening the pull requests for your repository. Select Git → GitHub → View Pull Requests. You can also search for the command in the Command Palette with Ctrl+Shift+P. From here, Visual Studio will load all the PRs in the repo and group them to the ones that are assigned to m...
VSLive! @ Microsoft HQ: Developer Takeaways and Must-Watch Sessions
VSLive! @ Microsoft HQ 2026 was one of the most energizing VSLive! events I’ve attended. What stood out was the level of engagement over five days of learning and conversation from July 27 through July 31. Developers came ready to dig into the future of Visual Studio, .NET, and AI-assisted software development, and many Microsoft engineers and product managers were there to have those conversations directly. If you weren’t able to join us in Redmond, there’s still plenty you can take away from the event. The Microsoft-led sessions were recorded, so you can catch up on many of the topics that generated som...
The Visual Studio Debugger Agentic Workflow Gets a Test-Driven Upgrade
A few months ago, we introduced a new guided agentic workflow in the Visual Studio Debugger Agent designed to help you move from a bug report to a verified fix without spending your morning guessing where to begin. If you missed that announcement, check out Stop Hunting Bugs: Meet the New Visual Studio Debugger Agent to see how the Agent builds a hypothesis, guides the debugger, investigates your application at runtime, and validates the final change. Today, we’re building on that experience with a new Test-Driven Investigation workflow. The Debugger Agent can now create or identify a focused test, debug th...
Visual Studio August Update – Work Smarter Across Models and Branches
Tune Copilot model thinking effort, share custom agents across your organization, track usage, and simplify complex Git workflows with worktrees and submodule support.
Unlocking the Power of AI for Every Developer in Visual Studio with Bring your Own Model
The best AI in Visual Studio is the AI you can bring with you. Developers don't work in a single-model world anymore. You might reach for one model for everyday coding, another for a domain-specific problem, and an approved model for work that must stay within your organization's governance boundaries. So, the question we hear most often isn't which model is best. It's, can I use mine? We're bringing Bring Your Own Model (BYOM) in Preview to Visual Studio, making it available and enabled by default across Community, Professional, and Enterprise SKUs. This Preview focuses on the developer experience available t...