Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Code, Cloud & AI

Code, Cloud & AI artwork

Why Visual Studio Is Thriving in the Age of AI with Mads Kristensen

Jul 14, 202637 minAudio

In this episode, I sat down with Mads Kristensen, a principal product manager from the Visual Studio team to unpack what a PM actually does inside a large engineering organization and how that role blends user research, roadmap planning, technical decision-making, and product experimentation. We talked about his 15+ years working on Visual Studio, why he still builds extensions himself to test ideas quickly with real users, and how Visual Studio continues to grow even in the middle of all the noise around AI-powered coding tools. He also shared why Visual Studio remains especially strong for professional C# and C++ developers, enterprise teams, and anyone who treats code as a long-term asset rather than just a throwaway artifact. We also got into what’s next for Visual Studio: deeper AI integration, especially around debugging, testing, code review, and project scaffolding, while still preserving the strengths that make the IDE unique. Along the way, we covered some lesser-known but powerful features like Dev Tunnels, saved window layouts, and floating tool windows, plus the move to yearly Visual Studio naming with evergreen in-place updates. If you’re a longtime Visual Studio user, curious about where the product is headed, or wondering how AI fits into serious software development, this conversation is packed with practical insight and a lot to be excited about. People / Social • Mads Kristensen on X/Twitter (@mkristensen): https://twitter.com/mkristensen • Mads Kristensen's blog (Fancy Zones + Visual Studio post referenced): https://www.madskristensen.net • Mads Kristensen on GitHub: https://github.com/madskristensen Microsoft / Visual Studio • Visual Studio: https://visualstudio.microsoft.com • Visual Studio Insiders / Preview channel (recommended in the episode): https://visualstudio.microsoft.com/vs/preview/ • Visual Studio Marketplace (extensions): https://marketplace.visualstudio.com • Visual Studio Code: https://code.visualstudio.com • GitHub Copilot: https://github.com/features/copilot • GitHub Copilot CLI: https://docs.github.com/copilot/github-copilot-in-the-cli • Microsoft PowerToys: https://learn.microsoft.com/windows/powertoys/ • PowerToys FancyZones: https://learn.microsoft.com/windows/powertoys/fancyzones • Dev Tunnels (mentioned as "DevTunnel"): https://learn.microsoft.com/azure/developer/dev-tunnels/overview • .HTTP file support in Visual Studio: https://learn.microsoft.com/aspnet/core/test/http-files • Hot Reload (.NET): https://learn.microsoft.com/visualstudio/debugger/hot-reload • ASP.NET (web apps referenced): https://dotnet.microsoft.com/apps/aspnet • WPF: https://learn.microsoft.com/dotnet/desktop/wpf/

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Barry LuijbregtsSo, again, it's it's great to meet you

Mads Kristensenfor the first time. Thank you very much for doing this. Yeah. I'm I'm happy to be here. Nice to meet you as well.

Barry LuijbregtsSo I looked you up, of course, and I see that your title is principal product manager. What what is that? Can you explain what that is? I have no idea.

Mads KristensenWell, I think that yeah. And I understand why you have no idea because I think it's different for every company. Like, the term product manager means different things to different people. We were used to call be called program managers, but the industry kinda adopted product manager. So what it is is, like, it's a technical role in the engineering org. So whether it's, you know, as you work on the Windows team or Office or as I do on the Visual Studio team, you work with the engineers, but you're the PM. And so the responsibility of the PM,

again, it varies from team to team and and Yeah. All even from PM to PM. But it's basically the person that, you know, understand the users, sets the road map, works with the engineering to build the features that they want, the help they design the features often with the users. And so it's a it's a very kinda user focused role, and it's also some there's some project management in it as well. Right? Because you wanna make sure you have the release notes that go out at the right time when you when you release the features that you've helped build them. And all that stuff, the go to market stuff.

So there's a bunch of of project management. But as a PM, you can kind of you know, as you find out where your passions lie and where your interests are over time, you can you can put yourself on the spectrum where you might have project management on one end of the spectrum and, like, highly technical stuff on the other side, like, built maybe, like, to the point where you built the features yourself to an extent. Yeah. And you find yourself where where are you the most happy and most effective on that spectrum?

And so I think that's why the when you ask that question, and I say, oh, well, it depends. I think it depends on where you are. And there might be other pivots as well. It might not be just the project management versus technical. There might be others, you know, things as well you can you can put yourself on. So I I I'd look at myself as somewhat closer to the technical and less on the project management. So I'm very involved with the users, very much out there, conferences and social media and stuff, and listening and understanding and

being the internal advocate of the users. So I take all that feedback into the teams and help build Visual Studio in accordance to what the users need, both what they tell me they need today, but what I can understand they probably will need in the future as well, which is it it becomes an art form at that point.

Barry LuijbregtsYeah. And and how long have you been doing that for Visual Studio?

Mads KristensenFor fifth over fifteen years now. Wow. Yeah. That's very cool. And I was an engineer before, so I came from the world of like, I was a Visual Studio user for ten years before I joined Microsoft, you know, in startup companies and all that. So I I used to be the people I'm building, which would for today. Right? Yeah.

Barry LuijbregtsThat's very cool. And I noticed that you build still a lot because when I look for an extension, your name shows up a lot with all sorts of extensions.

Mads KristensenYeah. I cannot because it's, you know, this it's the shortest if I have an idea and I don't know if it's a good idea or not or I don't know if my vision of how it should work or be implemented is right or wrong, then the fastest way is to, like, create it and then give it to the user and say, hey. What do you think? Mhmm. Yep. Then figure out how do they use it, what are the patterns, what don't they like, and then accept pull requests and comments and, you know, issues on GitHub so that it becomes like a fast feedback loop. And then very quickly, I can go back to the team and say, hey. Look. I made an experiment.

We iterated on it. These were the issues. Here were the fixes. Here's where we still have some opportunity for improvement, blah blah blah. And so that kind of replaces a spec. Yeah. Or it or it helps the spec because it's like it literally shows the screens, the the click stops, everything like that. Right? It's like a highly advanced mock up that you would normally maybe give to an engineering team.

Barry LuijbregtsOh, I never thought of it that way, but that that makes so much sense. It's like a proof of concept of something that you think people want, and then you actually make it and people can directly use it without actually baking it into the product.

Mads KristensenYeah. And sometimes we do bake it into the product. It starts its life like that. It might have been something that's been on a feature request for a long time, and then I'm like, okay. I now I have a need for it or I have a vision for how we can do it the right way, and so I go ahead and build it. And that can be the beginning of a way to build something in, or it can just be a way to say, hey. There's a bunch of people that want it. Let me just provide them that right now. And it could be years down the line before it reaches a per a priority level that we wanna build it in. Yeah. Because of other reasons.

So it's there's not always a one to one, like, in the here and now. Sometimes it takes years for it to be relevant to the team to bring in, but then we already have years of, like, refinement and iteration that makes it super high quality.

Barry LuijbregtsYeah. And people actually using it. That that's perfect. Yeah. Yeah. Oh, that is so cool. And then so you come up with everything, maybe with colleagues as well, colleague product managers? Are you the only one? Yeah. No. Of Visual Studio?

Mads KristensenNo. No. No. There's a bunch.

Barry LuijbregtsMhmm.

Mads KristensenWe have a lot more engineers than we have PMs for you know? And that's a good thing. Yeah. You there's definitely a thing is too many PMs. So I think we've already have a had a a kind of a lean PM team, but it's I think it's leaner now, which is kinda it works out pretty well. So, yeah, we're we're, like, on the PM side, on the core Visual Studio team. I think we're about I don't even know. I'm just get I'm just gonna give you a number. 12 PMs.

Wow. But that includes, like, PM managers as well. Yeah. Okay. Of which we don't have that many, like, two or something, two or three. But then you have all the other other team that also contribute into Visual Studio that are not part of the core team. So for instance, the dot net team and the c plus plus team. Okay. Now they build the runtimes. Right? And they build all the CLI stuff, and they build Versus Codex, and and they do all sorts of other things, but they have dedicated engineers and PMs that work on Visual Studio tooling for dot net and for c plus plus and so on. Okay.

Yeah. So they're they're PM for Visual Studio as well. They're just not part of the core team. So if you if you, like, kind of combine it all, I'm I'm sure we're about, like, I don't know, 25 PMs. And and that goes up and down depending on where people are needed in the moment. Sometimes you move and do something else. You come back and do other features and so on. Or you have teams that come in and say, hey. I'm gonna we're gonna build an Azure feature into Visual Studio. But then when we're done, we're not we're gonna move on and do something else. Yeah. Right. Yeah. So they're only part of the team for, like, let's say, two months, and then they're elsewhere. Okay. So it's a it's a huge organization just for Visual Studio alone. I didn't realize that. No. It's not well,

depends on what you Sounds good. Yeah. Yeah. But it depends what you mean by huge. I don't see it as such. You know, I we used to say we're over 250 people, but it, you know, but it comes in waves because, you know, as I wasn't what I what I was just mentioning. But I don't know if we're more than a 150 today, which is big for one product. But when you consider that Visual Studio is one of the largest software products in the world Yeah. By far the biggest WPF app, right,

and maybe dot net app as well. Yeah. But just in in general, like, we don't we don't even know how many lines of code we got, but it's it's in the millions and millions and millions. So Yeah.

Barry LuijbregtsOkay. So very important. And and and, I guess, a huge install base. Like, do you have kind of a a guesstimate of how many people use this?

Mads KristensenOh, yeah. We're in the double digit millions.

Barry LuijbregtsReally? Wow. Amazing.

Mads KristensenAnd and the number is not you know, you would think maybe that, oh, nowadays, everyone is just using, you know, Claude code or, you know, CLI or Copilot CLI or Versus Code or, you know, Cursor or because those products and the users of them are very loud and dominant on social media, you would think that Visual Studio numbers are going down, but they're not. They're they're going up. They're going up. Oh, that's good. Yep. Visual Studio is actually very, very healthy

even though you don't hear as much about it. It's not as visible maybe as it used to be because it drowns out a little bit in all this especially nowadays with all the AI, like, in all the hysteria of of that. And so but but, no, Visual Studio is is doing quite phenomenally, and I think has found a really sweet spot in the world of, you know, AI versus, like, people who either don't want to use it or just use it occasionally or who are not allowed to use it because of, you know, security or whatever concerns their organization might have. Right?

Yeah. So so Visual Studio is somewhere in between where, like, it it's getting really good at AI. The way Visual Studio does it is a little bit different than the others, and that's on purpose because we we have a different cohort of users than others. Like, Versus Code, for instance, has to be pretty broad. Like, they you know, whether you're a student or data scientist, beginner, advanced, web developer, back end developer, game developer, like, they they target pretty much everybody very generally. Visual Studio is very

narrow. It's like professional developers, c sharp and c plus plus. That's what we go for. Enterprise often because it's the pro developer segment. And so the concerns and the the habits and the priorities of that cohort is just different. And so the way we lean into that has been kind of unique, I think, in the industry and and it being pretty successful because we're really good at both doing the AI stuff, and we have to be loud about that. And so some people are like, oh, it's every everything is about AI in Visual Studio. It's like, no. It's not. We're actually really good at

doing a bunch of features that has nothing to do with AI. And so we do both, and and we do that with with quite the success. So it's not doesn't mean that we're perfect or that we don't have any room to improve, of course, but it means that we I think we found finally a sweet spot where we can cater to both the people who use AI every day, all day long, and the people who don't use it at all and anywhere in between as long as they're Pro, C Sharp, and C plus plus Yeah.

Barry LuijbregtsThat that makes me very happy to hear that it is still going strong and even going up because I am a Visual Studio user from back in the day. You know, always did Visual Studio and then Versus Code came out and I was like, I need to do so much myself. Extensions, CLI stuff, terminal. Okay. It's not not my thing. I like visual visual studio, so I like to see things and click on it and do things in a simple way. Debugging is a very strong thing for instance in Visual Studio. It's easy to make things run. You just click the button and it starts to run. That's what I like. I I liked it a lot. And like you said, AI, I use that a lot as well. I get the Copilot for instance. But it's also right in there, so you can just use that.

It's slightly different from Visual Studio CodePilot and Versus Code, but not that much, I think.

Mads KristensenNo. And and it's the gap is also closing. I think the if you're on the insiders Yeah. Which is our kind of our preview release for you to get early access to the bits Visual Studio, you'll see that it's it's getting better so much faster now. And so I'm on internal builds, and I'm having an absolute fantastic time. I I just think that the quality has gone up so much and the speed and the execution. Everything is just better. So I'm very, very happy about that. And so you're gonna see that gap closing, but it's not gonna close completely. It never will because we are targeting other things. So you were mentioning the debugger.

We have probably arguably the best debugger in the industry, and there are things we can do that no one else can do because we have that debugger. And and if we we there are ways we can tie AI into the debugger that makes you even better at debugging. Yeah. It's about returning power to you because how do you how do you make sense of, like, some issue you're having in some sort of async call where you don't know exactly what the issue is? You maybe you run stuff in parallel on background threads, and it can be really hard sometimes to debug really complicated things. So how do we use AI to solve that problem? We haven't been able to solve it before.

There are certain problems that you can't solve in a deterministic way. Yeah. And everyone's app is different. So debugger scenario is very is is an is an obvious thing that we can add special value through AI. Now other IDs and and and editors out there cannot do that because they don't have a tight integration to a a really powerful debugger. So we have an edge there, and we're leaning into that because that actually is something that's a very pro

use case. There are other things about unit testing, for instance, that that lends itself very well to that. Creating new projects from scratch, again, is something that you can't do in a deterministic way. You have to have some sort of AI because everybody's project is different. So there are certain things that we're looking into. Like, if you wanna create a new website I'm just making making this up. Right? Let's say you wanna build a new website. You wanna build one you have a customer that wants a bakery website for their new bakery.

And so you can go in and say, file new project, and you can choose asp.net web application. And that gets you kind of to, like, a hello world type of situation, and then you have to do the whole bakery thing. But what happens if you go and say, hey. I want a bakery website. Right? And and you can then be asked for clarification. Hey. Do you want, you know, an app to go with that for, like, return customers so there's a loyalty program? Do you want it can start to ask you all those questions. Right? And so your starting point when you're done scaffolding

and have to go to work is, like, much closer to the end result than it was in the past. And Visual Studio has this rich templating mechanism. Right? We've always had that. Yeah. Text editors don't have that, so they can't lean into it in the same way we can. So it's about leaning into some of those things that makes Visual Studio Visual Studio. It's not just about, like, the chat and, you know it's also about that, but it's not only about that. It's also about the special things in Visual Studio.

Barry LuijbregtsYeah. And I like that. That's why I still use Visual Studio and also with AI because there, when I hit an exception and the debugger pops up, then I can click my Copilot thing and I say help me with this exception and then it can actually read the variables and all the things around there and use that as context, which I cannot do yet maybe in Visas code and I don't know if that will ever happen because there's not a strong link there with with debugger.

Mads KristensenYeah. It is something we're looking at, but the but that's exactly right. So I I think Visual Studio is the is the tool and will remain the tool for developers who really value code as an asset. Like, there are there are certain code that is that's not an asset. That's just an artifact. Yeah. Like, if you write proof of concept prototypes, it could be side projects, small things, throwaway things, internal tools, or whatever. You don't really care about code. Like, you don't have to maintain the code for years to come

as a team of engineers. If all your interaction with the code is that it just generates and you just ask the AI to fix it if there's an issue and you don't actually look at the code and you don't really care, you know, you can use whatever tool you want. You can use Visual Studio. You can also use the CLI. You can you can use whatever, and you're gonna have a great time. But if code is an asset to you, if it matters how it's formatted, if you're gonna review it, if there's pull request and peer reviews and all those type of things where it really matters

that it's high quality and has a high maintainability score and all that type of stuff, Visual Studio is for you. Like, that is, like, hands down. That does not change because AI comes into the picture. In fact, we're gonna double down on a bunch of these things so that even if you're using AI, we're gonna make sure that you're gonna have kind of that enterprise grade code quality that you had when you wrote everything out by hand. And so you might still write a bunch of stuff by hand, but it it you might also have some things written by Copilot, let's say. Right? And so

have all that done in a way that's, like, exactly how you or your team wanted to look and act and all the tough stuff. And so it's, again, it's about quality. It's about seeing your code as an asset. That's really what Visual Studio is about.

Barry LuijbregtsAnd and how do you do that yourself? Like, when you write extensions, for instance, do you still write code by hand, or do you just tell the AI to do it?

Mads KristensenI tell the AI to do it mostly. I have. You know? But the thing about but that's but hang on. It's because that none of my code goes into Visual Studio. It never did, even when I wrote it by hand. Right? The engineering team, they have their quality gates. They have a bunch of things that they do that I don't have to do when I write an extension. I don't fall under those same quality concerns or whatever. Right? And I don't have to maintain it over time to the same extent. Like, I don't have to have a whole team to being able to, you know, maintain it for years down the line.

It's just me. Yeah. Yeah. But yeah. Yeah. Well, I don't care. I don't I I for me for me, some of a bunch of my code is just an artifact. Yeah. I get that. And and there's no shame in generating codes. That's kinda what the AI does. You know, it's funny because, first of all, I I that's I agree, but I will I will say I would not the way I do it, the way I code with just the AI, I would not consider an asset. Like, I would not be someone that'd be proud of it or present it to my team and say, hey. Look at can you do a code review here? Like, I was like, no. Don't don't review this code. I know I can go through and be like,

no. You know? I I don't I don't like it, but I but I don't feel like I need to. So in this case, I don't need to. Yeah. But every project is different. Right? You're everything is different. What I really like about Visual Studio is I stay in there, and when I debug, I have to debug it. Like, I'm still the best debugger between me and the AI, hands down. Yeah. No matter who wrote the code, I can debug. And I'm not even a great debug person at all. I'm not very low level, but I'm still better than the AI. So having it all happen in Visual Studio I'm not using the CLI. I use it sometimes for some other things, but not for writing code.

I use Visual Studio. I wanna see what happens. I want I still wanna understand what's going on because I still need to steer it because I know what some of the caveats are for the in the Visual Studio extensibility model. I know some of these things. And and using my expertise, I'm the domain expert here over AI even though it has it knows stuff I don't know sometimes. You know? I'm very impressed by it. But I'm I'm kinda still looking at what it's doing while it's doing it and correcting it when I see that it goes down a wrong path.

And if I didn't do that, I wouldn't be as fast. I wouldn't be as effective. I wouldn't be able to ship as many extensions that I've done. I think I've done 12 extensions in the past, like, four months. Wow. Yeah. Productivity booster. Absolutely. Oh, my my main two. But but, again, the only reason I'm, like, 10 x in my productivity or five x or something right now is because I don't have that code maintainability issue. Yeah. Or not issue. Right? It's like I don't the code is not an asset for me in this particular case.

Barry LuijbregtsYeah. Exactly. Yeah. Yeah. I got it. So I wanted to ask you this. What is your favorite feature of Visual Studio?

Mads KristensenOh, man. Don't make me choose between my children here. Okay. Or

Barry Luijbregtsa favorite.

Mads KristensenYeah. Yeah. Yeah. I'm very big on the small things, the quality of life, delighters. So something as simple as holding down shift while scrolling the mouse to do horizontal scrolling in the editor. Do I use it all the time? No. But I love that it's there. The fact that I can hover over any reference to an image, like, it's a HTML file that have an image tag and then it has, like, some sort of path, I can just hover over that and see what the image looks like

and the size of it. Like Yeah. Small things that help me answer questions that otherwise would have taken me not necessarily a long time, but a little bit of effort to find out. I I'm very big into that type of stuff. I think Visual Studio is so good. All those the the big things for me has been kinda taken care of. Like, I can do those big thing. I can create WPF applications, right, that do amazing things on the desk desktop or APIs for, you know, or or web web files sorry, websites and so on.

So so for me, it's the quality of life. Like, do I wanna stay in Visual Studio all day long, seven days a week, or five days a week. Right? Mhmm. Eight hours to ten hours? And what are the things that make me go get angry or annoyed? What are the paper cuts? What are the things that you know, it's like it's like your own house. Like, if if you if your home office you're in or whatever has, like, a a color wall you don't like, you wanna change it. You're gonna feel better sitting there all day long. You're gonna be more excited to go to work.

So I I wanna find and it it it and it there's a correlation between that and then, I think, other users. So the reason I wake up in the morning, the reason I work on Visual Studio is because I wanna make Visual Studio, like, a thing that makes people excited to start their workday in the morning. And I think a lot of it is those little things. Now those little things, they have to you have to have the fundamentals right, like no bugs, no issues that are, like, annoying or sorry, not annoying, but blocking you. Like, those fundamentals have to be in place first.

You have to be able to actually perform the task you wanna do, and then you can add the delighter layer layer you know, that can come later. Now we work on all of those things in parallel. Like, think everybody does. Right? Yeah. But but those are the things that stick out to me because those are the things that make me smile.

Barry LuijbregtsThat's yeah. That's lovely. Things that delight you. I like that. Mhmm. And and and maybe what are what is one thing that you think almost nobody knows about that's in Visual Studio?

Mads KristensenI think there's a lot of things people don't know about Visual Studio. I I give a I give a talk called forgotten things you didn't know you needed in Visual Studio. Oh, cool. Because there there's just so many features. If you're a web developer or something, a feature called DevTunnels is probably not one you've used. We don't see a lot of usage of it, but it's absolutely phenomenal. You're, like, you're nodding. I can say you know what it is. But the fact that you can it solves that ancient in in today's world, that ancient issue

where you're sitting inside your corporate firewall and you build a website and you wanna see what it looks like on a phone, on an iPad, all that, see how it renders correctly. And how do you do that without deploying it to, a public endpoint that you can type the URL into your device? Right? DevTunnel solves that. Microsoft's foot we foot the bill so that we open a a channel between your local host, basically, and the outside world, and you can just in any in any on any device, can access your local machine's website running right there. So that's that's a huge one for for web development,

one that I really like. General stuff that people don't use because probably they don't don't know about our saved window layouts is one that I'm very happy about. I don't use that. I don't know. Yeah. A lot of people don't use it. It's funny because I use it all the time. But because I, you know, I have to move from, like, a laptop to then into a docking station where I have bigger monitors and so on. So being able to move with one one click,

change your layout of where your solution explorer and your output window and, you know, your Copilot chat window and all those different things are laid out is super important. I because I can go from one perfect setup to the next perfect setup within the constraints I have with the monitor size and how many monitors I have and all those type of things. Okay. So so that's huge. And in that same vein, I wrote a blog post recently. You know, Fancy Zones is a is a feature out of what's called Microsoft PowerToys.

It allows you to take any window and, like, snap into, like, certain positions around the screen. Windows have some of it built in. You can, like, snap to the right or to the left, but this one allows you to do completely customized zones. And there's a setting inside Visual Studio that can make all tool windows have their own be like their own window. They show up in the taskbar, but you can snap them to a fancy zone. So if you have multiple monitors, you can you can, like, just detach

like, solution explorer, test explorer is a very common one because people wanna expand that, have it out large. Just put that over on a separate monitor, and you can, like, snap it into place. You can maybe have it side by side with something else that you wanna look at on that secondary monitor. And so people don't know you can do that. It's not enabled by default because I think that most people don't have that setup or that need. Mhmm. And a lot of people do, and so finding that setting is really nice. Just search for the word float in the settings.

Barry LuijbregtsI'm gonna try that one. That's cool. Okay. Cool. So that's that's already a lot of stuff. Maybe a last topic that we can go into. I really like that we now have Visual Studio 2026 because it's beautiful, it's snappy. Finally, it's just lovely. I create Pluralsight courses, and I'm just about to create a Pluralsight course about debugging and testing for 2026. And then I heard there's a Visual Studio 2027 coming. So

is is that true, and and what's in it?

Mads KristensenYeah. That is true. And there's Visual Studio 2028 and 2029 and so on. So every year, starting with the 2026 release in November 2025, every November, we're gonna rev the the version number

Barry Luijbregtsto

Mads Kristensenbe the next year's version. So Visual Studio 2027 will we will release that in November 2026 and so on and so forth. Okay. But it's not gonna be a side by side install. You know? Right now, you can have 2022 and 2026 installed side by side. Yeah. That's not what this is. This is think of this as now Visual Studio's evergreen. Mhmm. K. It's an in place update. You just take the next so when you when you reach November and you have Visual Studio 2026 and it says, hey. There's an update just like you have today. It says, hey. There's an update. Do you wanna click update? You do that, and then all of sudden, it's just called 2027,

but it's just an update. K? Now there could be something under the hood that's different. Like extensibility models, API versions, and so on could change, but it wouldn't affect you. It would would affect other things, but but that's happening. This this is how we're doing it these days. So Good. Yes. So it it means that at some point, you can just refer to it as as Visual Studio. Yeah. Right? And and the year is just a way of saying, hey. I got the April update of Visual Studio 2026.

Like, otherwise, how would you reason about what version it is? Yeah. Very version. Very easy when you just say, hey. It's the month of 2027. Right? Like Yeah. April 2027. That's the update I'm on. And so it makes that version thing so much simpler.

Barry LuijbregtsAh, okay. Yeah. Yeah. Okay. So it's not a huge breaking change. It's an update.

Mads KristensenYes.

Barry LuijbregtsOkay.

Mads KristensenGone are the days of of breaking changes, you know, knock on wood, because we we separated the the runtimes and the build tools, the tool sets, and all that for c plus plus and .net or whatever to run independently of how we version and and ship updates to Visual Studio, the IDE. And so they're not detached, which means you can update the IDE without updating your build tools. And so you can you can always be in the latest feature set, but then whenever you're ready, your team is ready, you can update your your tool sets.

And that's important because, you know, when you when we ship Visual Studio on a monthly basis, we want you to take those updates. You also probably wanna take those updates, But you couldn't in the past because you said, no. No. I have to be on this old version because we're only running on, you know, this this version of the c plus plus toolset or whatever. And so now those are separate, and they update on their own cadence and Visual Studio supports it all.

Barry LuijbregtsVery cool. Okay. And are there any very exciting new features coming, like big things that you can talk about?

Mads KristensenI think we have we have a lot of stuff cooking right now. A bunch of AI tools, a lot of refinements, a lot of delighters coming Mhmm. A lot of fixes. We're fixing more bugs now than we ever have before. It's not because people are reporting more bugs. It's because we're our focus has has been changed a lot over the past two, three years to really focus on what the users are asking us to do. Right? Right. You could think, oh, why didn't you do that before? Well, reasons.

Bad ones. So it's like we're we're that's something we're really keen on. Like, what are the things we can do to put a smile on people's face? How can we lean into the strengths of Visual Studio? I think you're gonna see more coming in. Like, we're gonna continue evolving the debugger. Like, it's gonna it's just getting better and better all the time. But there are other things that's gonna be better. I think you're gonna see test different ways. You know, unit testing is gonna be improved.

Stuff like reviewing code, PRs, that type of stuff is gonna be improved a lot as well. And the reason for that, of course, is that, you know, when you have AI, you know, writing parts of your code base, you need to have guardrails in place. Right? So that's why unit testing all of a sudden becomes this very important thing where that has to be top notch. So you can have your guardrails ready. Otherwise, you can't really unleash agents to do work if you if you can't have some sort of trust that it won't break stuff.

Barry LuijbregtsYeah.

Mads KristensenBut everybody benefits from that. Everybody has a better unit testing. That's that's kind of where that's the that's the kind of the balance I was talking about in the beginning we're trying to look at. How can we make everybody better, but also, like, by leaning into what Visual Studio is already good at and the use cases you use Visual Studio for, and then how a can AI then augment that to make it even better for people who opt into that. Right? Yeah. So PR is like reviewing code, making sure that your code is like it would also be nice if you can before you commit, you can make sure that your all your coding styles,

code standards, all that has been taken care of so that you don't spend time reviewing code, and they just you just look at code styles. It turns out according to GitHub, they did a cert survey or some sort of stuff some years ago. I think it was 25% of code reviews are spent on coding standard. Oh, okay. So it would be really nice if we could just get rid of that, you know, by having it done automatically or having it done while you write the code or whatever it is. And so that benefits both the agent agent work that it will write according to your standards,

but also for your own stuff. So you don't send up you know, waste 25% of code reviews thinking about that aspect.

Barry LuijbregtsYeah. Okay. Well, those are all great features. Quality of codes so that you can unleash agents to just write stuff, and then you can review it properly. You can test it properly. All those things are super important and the debugger as well. That I I like that a lot because I use that all day. So that's that's great. And then you'll you're gonna continue to see updates to all sorts of features also. Like, hot reload is getting better and faster.

Mads KristensenHTTP file features are are getting better and more pretty and and bet you know, all the time. So so everything everything is gonna be lifted. Like, we're we're gonna make everything better, but I just mentioned a few kinda key areas that we're very interested in because it it fits that sweet spot between people using AI, people use it occasionally, and people who don't. Yeah. Everybody wins when we do those balanced things. And so there are some big buckets

that, like, falls, like, right into that.

Barry LuijbregtsOkay. Cool. Well, I look forward to all that stuff. It will come. I will just update Visual Studio, and boom, it it will be there at some some point.

Mads KristensenYeah. Get get the in insiders. You might already be on it, but maybe the listener out there are just using the Stable channel, which is cool too. But if you really wanna get early access to all the latest and greatest, you're gonna be a month ahead of the game. We released the insiders a month ahead of of the stable channel, so you you kinda get the heads up there. And and you'll see that there's so much churn every day. I get the daily builds inside, and, like, every day, it's getting like, you can you can just tell. It's better every day. It's it's small things, sometimes bigger things, and

so get the insiders. I think you'll enjoy it.

Barry LuijbregtsAlright. I'll put a link to that in the show notes as well. Is there anything else that you want to share, like, where people can find you personally?

Mads KristensenOn Twitter. I think that's the or X rather. I think that's the most direct. So my Twitter analyst is m Christensen on on X, and I, you know, I I keep it to pretty much just Visual Studio stuff. So so there's a lot of I do a lot of, like, teasing new features, screenshots I just get from the engineering team. And so if you wanna see what what's right now, what do we have on the internal builds, what's coming, even before it hits the insiders,

yeah, you wanna you wanna follow me on on on x? I I spill all the secrets there. Okay.

Barry LuijbregtsOkay. So everybody go look there and connect there. Alright. Yes. Excellent. Thank you very much for talking with me today.

Mads KristensenYeah. Thanks for having me on.

Open the transcript file

Hosts and Guests

Hosts

  • Barry Luijbregts Host Feed-stated

Guests

  • Mads Kristensen Guest Feed-stated

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Why Senior Engineers Matter More in the Age of AI Agents with Albert Tanure

    Oct 25, 202638 minAudio

    In this episode, I sat down with Albert Tanure, a Senior Cloud Solution Architect at Microsoft, to talk about what AI is really changing in day-to-day engineering work - and what still matters just as much as ever. We...

    Credit the people on this episode

  2. From Big Data to Agentic AI with Microsoft Foundry with Heena Refai

    Sep 15, 202638 minAudio

    In this episode, I sat down with Heena Refai, a Cloud Solution Architect at Microsoft, to talk about how enterprise AI has evolved from the big-data and traditional machine learning era into today’s generative AI and...

    Credit the people on this episode

  3. Rob Bos on GitHub Copilot, AI Engineering Fluency, and Better Software Delivery

    Sep 8, 202641 minAudio

    In this episode, I sat down with Rob Bos to talk about what’s happening across GitHub, Azure DevOps, GitHub Advanced Security, and the fast-moving world of GitHub Copilot. Rob shared how his work evolved from DevOps...

    Credit the people on this episode

  4. From Autocomplete to Agents: How Anton Sizikov Uses GitHub Copilot Today

    Sep 1, 202649 minAudio

    In this episode, I sat down with Anton Sizikov from GitHub to talk about how AI coding tools have evolved from “smart autocomplete” into full-blown agentic workflows. We unpacked the early days of GitHub Copilot, when...

    Credit the people on this episode

  5. Agentic Development Is Forcing Us to Become Better Engineers with Jon Galloway

    Aug 25, 202637 minAudio

    In this episode, I sat down with Jon Galloway to talk about what agentic development actually looks like in practice inside Microsoft and out in the real world. We explored how AI-assisted software development is...

    Credit the people on this episode