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...