On today's #VSToolbox replay episode, we get a behind the scenes look at how performance is measured and what improvements were made in #VisualStudio 2026. Drop in, msft.it/63329tmThT
David Kean
@keansbox.com
I make things fast @ Visual Studio, previously NET. He/Him.
Great behind the scenes walkthrough by @keansbox.com on how the VS team keeps grinding on improving performance in Visual Studio. www.youtube.com/watch?v=MNT-...
Performance Improvements in Visual Studio 2026
YouTube video by Microsoft Visual Studio
youtube.com
Been using it since it was released. Rock solid and performance is great. It’s my new daily driver.
Visual Studio 2026 represents about a year's worth of work across the Visual Studio team. If you haven't tried it, head over to visualstudio.microsoft.com/insiders/ to download it - it will install alongside Visual Studio 2022 so you can continue to use both if you like.
Visual Studio 2026 represents about a year's worth of work across the Visual Studio team. If you haven't tried it, head over to visualstudio.microsoft.com/insiders/ to download it - it will install alongside Visual Studio 2022 so you can continue to use both if you like.
Visual Studio 2026 Insiders - Faster, smarter IDE
Try Visual Studio 2026 Insiders with Copilot AI deeply integrated, faster performance across C# and C++, and a refreshed, modern UI.
visualstudio.microsoft.com
The startup time on the new Visual Studio 2026 preview is really impressive. Even for a very large 100+ project solution, it opens in just a few seconds.
Gotta say that in other news - I’m really enjoying the new #vs2026 insiders version. Not one crash and now it’s my primary IDE . Seems snappier and cleaner. Great job #VisualStudio team. And shout out to #SSMS team! V21 is breath of fresh air.
Welcome to Visual Studio 2026 Insiders: devblogs.microsoft.com/visualstudio... I haven't posted much for a while as I've been heads down working with the Visual Studio team to deliver all the performance and other goodness in this one.
Visual Studio 2026 Insiders is here! - Visual Studio Blog
Visual Studio 2026 Insiders is here – and it marks one of the most ambitious steps forward we’ve taken with the IDE. This release brings AI woven directly into the developer workflow, performance impr...
devblogs.microsoft.com
. @vscode.dev What happened here, I find it super hard to find the commands I actually want to click on this. 5 ways to split, probably unneeded?
We've been working on vNext (devblogs.microsoft.com/visualstudio...) and some early feedback shows that we've really hit the mark on this one.
🎉 Visual Studio 2022 v17.14 is now generally available! - Visual Studio Blog
Visual Studio 2022 version 17.14 is now generally available, introducing agent mode, MCP support, AI doc comment generation, and a new monthly release cadence focused on Copilot and developer producti...
devblogs.microsoft.com
One time during .NET Core early days, we were having a remote meeting with Fowler and another colleague of his. This was in the days when video meetings were a bit unusual. His colleague completely forgot he was on video and had a reaction like this to something I said.
Caught a snapshot of myself in a meeting reacting to something.
@ticketmaster.com Your forced password reset as I logged in tonight blocked me from buying tickets on my android as i couldn't come up with a 12 digit password on the fly and put this in the "too hard basket"
Finally had time over the holidays to realize a long-standing dream of mine: a hex editor that knows about the PE file and .NET metadata format. You can click any byte and it will show you which data structure it is in the tree. Every byte is covered. The parser is at github.com/KirillOsenko...
Microsoft is actually going ahead with its Microsoft 365 app logo change 🥲
If you ever hit this sort of thing, just throw in a en.wikipedia.org/wiki/Zero-wi... and no one will ever know.
Spent an hour arguing with chatty about aligning some plotly graphs, and I'm no closer to aligning them. AMA.
On the hottest day of the year and power's gone off. Not a great start!
I'm throwing a party and trying to figure out cocktails. Let's say I can only make 4. What should i be making to cover all bases?
Did you know that you can define a DebuggerDisplayAttribute for a type from another assembly? Just add an assembly-level attribute to your code and specify the Target type: [assembly: DebuggerDisplay(@"\{Color = {Color}}", Target = typeof(Pen))]
We added a feature to Visual Studio to automatically detect when it uses an unusual amount of CPU. After 20 mins of continuous CPU across all threads combined (and the machine has been sampled), we capture a short trace.
When @nickcraver.com joined Microsoft I was curious what he will naturally gravitate towards after he looks around. Nick looked around and decided to fix builds! When @nguerrera.dev joined Microsoft, I already knew what he will deem to be most impactful task for starters: fixing builds!
I spend my day breaking builds, so thankful that these folks are there to pick up the pieces, including @kirillosenkov.com himself who has written the best tool to diagnose them msbuildlog.com!
MSBuild Log Viewer
msbuildlog.com
When @nickcraver.com joined Microsoft I was curious what he will naturally gravitate towards after he looks around. Nick looked around and decided to fix builds! When @nguerrera.dev joined Microsoft, I already knew what he will deem to be most impactful task for starters: fixing builds!
If there just one one skill or attribute that I think early in career folks should focus on, it would be, "be curious". This isn't "questioning every decision"-curious, but the "I wonder why it works this way, let me figure that out"-curious.
As part of planning what to work on next in the performance space for Visual Studio, we've been thinking a lot about "perceived" performance. Perceived performance is the time users "think" an operation takes, rather than the actual time it takes. 🧵
Sorry folks if you followed me in that other place and this a repeat but I can't bear to link to that place, and need a new version of this rant so that I can point to it. Asynchronous/Overlapped I/O will never be faster than synchronous reads. learn.microsoft.com/en-us/window... 🧵
Synchronous and Asynchronous I/O - Win32 apps
There are two types of input/output (I/O) synchronization: synchronous I/O and asynchronous I/O. Asynchronous I/O is also referred to as overlapped I/O.
learn.microsoft.com
Scaling is definitely going to be based on the workload you have, but it helps when the framework you build on top of gets out of the way of that.
Fun post. > a high number of concurrent tasks can consume a significant amount of memory Is ~400 megabytes for a million tasks significant? Ok 2.5gigabytes for Go is a bit much. But like if you have a million tasks is that amount of memory usage genuinely prohibitive?
Dramatically faster package restores with .NET 9’s new NuGet resolver
Dramatically faster package restores with .NET 9's new NuGet resolver - .NET Blog
.NET 9 introduces a new NuGet dependency graph resolver that dramatically improves package restore performance for large repositories. Learn how this reimagined approach reduces restore times from 30...
buff.ly