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.

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.

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

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.

@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"

Did a thing over the weekend, surrounded by friends and family.

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

In case you didn't know Visual Studio could do this: #dotnet #csharp

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!

Is it me or has Google stopped handling stock quotes?

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!

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.

Sick burn @blueskyroast.bsky.social, I think I'm going to put this on my profile page.

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

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.

Dramatically faster package restores with .NET 9’s new NuGet resolver

Ima going to take a wild guess that folks that work on Google Wallet have not lived in Australia. It is faster and easier for me to swipe a physical credit card to buy a coffee in Oz than it is to use my $2000 phone due to the forced biometric. How did we end up here?

A post from the archive 📫: Find the address of an object in Visual Studio https://www.poppastring.com/blog/find-the-address-of-an-object-in-visual-studio #debugging #visualstudio #diagnostics

My HP printer has been "running out of ink" for the past three years, AMA.

So weird, that same sentiment is also being thrown around by our Aussie contingent in Australia, and we don't celebrate it.

But you can take credit for those awesome .NET posters, right?

I'm assuming its machine-wide resource that's being blocked. 1) Use PerfView to collect, but check Thread Time (uncheck zip/merge). Leave everything else to default. 2) Record freeze, as short as possible will be easier.

Heard a version of this in a meeting once from a CLR director; "this is a solution in search of a problem."

Lists for blocking/muting are interesting, but I do wonder if they are ripe for exploitation? Provide a pretty useful list, wait for good penetration across Bluesky and then ask content providers to pony up money to avoid being added to list?

This is interesting and can't believe I missed this. A project by @xoofx.mastodon.social.ap.brid.gy. Super interested in the CPU usage visualization, and the automatic JIT, GC, kernel buckets, something I manually calculate today. Looks like a great companion next to PerfView.

That Gen2 callback is super clever and I haven't seen it before. Basically, when low on physical memory (< 10% free) during or around about the same time as that induced low memory Gen2 (github.com/Maoni0/mem-d...), ArrayPool makes its pooled arrays eligible for collection. 🧵

I've seen AI summary useful in few things: 1) Forum-like experiences where there's lots of comments from folks, and you just want to get to the bottom of the "real" issue(s) and conclusion 2) Chats (think Slack) where you want to catch up on what is being discussed. 3) Meetings

Them: Use memory-safe languages, you'll be free from a certain class of bugs. My JavaScript website running in Chrome:

Good read of @ericlaw.bsky.social's mistakes building Fiddler as a side-project while working at Microsoft. Super tempted to deep dive into that Thread Pool problem he hints at towards the start, something Visual Studio itself thinks about a lot! textslashplain.com/2024/11/24/f...

Extensions inherit the "targeting complexity" of their host. This is super difficult to talk about these things from a Microsoft perspective because most users/customers don't need to deal with this, and the ramifications of what happens when we try to change this.

I just found a cool feature in Visual Studio. I can grab a project and drag it to the other project to add a reference to that project. I had no idea. I thought it would be a nice experience if this worked... and it was 😍

These black Friday deals are amazing, anyone want me to them up a bottle (or two) at LAX duty-free?

On my last night in here, I got to hang out with some good friends, including my old work wife @terrajobst.net. Adiós Seattle, it was fun.

Woke up to a scurry of emails telling me my flight was cancelled and, then, a scurry of emails that it was rebooked for a later time. I'm super glad that was sorted while I was asleep.

I miss good coffee, but I completely forgot the US sells alcohol in a pharmacy, and I'm here for it!

When I left Redmond campus today, there were still whole families camped out there for what look like the long haul as they don't have power.

My new mantra, "Hey, instead making this progressive UI/async, how about we make it fast?"

Visual Studio 2022's splash screen shows up approx. 100ms later than Visual Studio 2013 manually testing it. This was confusing to me after I traced it, as relative to their main method entry point, they both take about the same amount of time to render and show the window. What was going on?