 Hey friends, I'm Scott Hanselman. The folks at visualstudio.com said that y'all wanted to see how I use Visual Studio. I'm not really sure why that would be interesting, but I figured it couldn't hurt. So I put together a small video here. Now you're looking at one of my monitors. I've actually got three 4k monitors that are kind of across each other, but I'm doing this one on a lower resolution center monitor. So you'll have to bear with me. Now I've got a number of Visual Studios actually on my machine. If I type in Visual Studio here in the start menu, you'll see a couple things. Visual Studio code, new icon, Visual Studio 2019, Visual Studio 2017 from before. Notice the green icon here from Visual Studio code insiders. That's a kind of a daily build. And then if I go to Visual Studio 2019, I actually have two Visual Studios installed. I've got an internal preview and Visual Studio 2019 itself. That's really cool because you can run these things side by side. I can install and install, update these, and if one doesn't work, I can use another one because it might not be like this is internal and that one's more stable. So that's cool. So if I go and say something like 2019 and launch that starts up right away and shows you the recent stuff, I could go and open a folder or even clone directly from GitHub, which is kind of cool. I've got my podcast that I'm working on. I'm porting. This is about a 15 or 16 year old app that I'm porting. This is an old web forms app. So the different things that I'm doing here, if I go and look at Hanselman, it's core. No, actually, this is my podcast site. So this one is for my podcast. Here I'll bring up, I'm using Edge, a canary version of Edge. So here's my podcast called Hanselman. So this website here is done in ASP.NET Core and hosted on Azure. It's a real website that I really care about. And if I go to dev.azure.com, I've got my main website and I've got my Hanselman, it's website and the pipeline that I can go and manage that. So here I'm updating and then releasing that out to production. So that's here in Visual Studio 2019. Now I'm using live unit testing, which is pretty cool. So here I've turned that on and you'll notice on the left hand side here, things are being covered by tests as I write code. Like so as I make a change to some code, let me see if I change that to like, I don't know, see how these all changed. I'm going to keep writing code and doing stuff. Look, I just broke, broke a test just while typing. I didn't compile. I didn't do anything. I didn't even save. Look at the little star there. I didn't even save this. You'd automatically notice that that was breaking a test. I'll go ahead and go back and undo that. I want to make sure that that does not break tests as I'm going around and working on my index pages. I can see coverage as I move through all of my things. Now that's live unit testing. I've got about 19 tests. Turns out I've actually got more tests than that. I should get 23 tests. Some of these tests use a thing called Selenium, which automates my browser and let me look at not unit tests per say, but full integration test. So here I am launching Selenium, which is going to go and launch Chrome. And you'll notice in a second it says Chrome is being controlled by automated test software. I could also launch Edge or Firefox. And that's going to go and talk to my actual back end. So this is more of a more of a smoke test. You'll notice that I've got 23 tests here in my test Explorer, but I've only got 19 in my regular tests. That's because four of these are these smoke tests and I really don't feel like I should run those during live unit testing because I have Chrome popping up all the time. Plus it doesn't really make sense. I want my live unit tests to go fast, fast, fast, fast. So what I can actually do here. Let's see if any of these fail. Oh, it's like one of them failed. You can actually see I've got a carriage return line feed here when I should not or at least I didn't expect one. So I either need to fix the test and what it's expected or maybe fix something else. But I want to point out that some of these are are skippable facts, meaning that they are tests that don't need to run. I don't want to run things if I'm in Docker or in a build server. So I have a little check for that. And I also want to make sure that my live unit testing live unit is not something that there you go. Look at that. The one of the traits of this test is that you skip it when live unit testing. So 19 tests here, 23 tests here and I could go in there and potentially fix that one. If I felt like it. I can go up here and let's go ahead and actually go there and then check out the web browser. You can see I can have Firefox Chrome Edge Canary pick those and then go ahead and start and go and debug my application. See my nice big green cool mouse there. I'm all about the giant mouse. You can go and start menu and type in mouse cursor and make that really big or rainbow or whatever makes you happy. Okay. This is going to go and launch my site. See look at that there. So that's interesting. I can go and maybe debug a particular issue in the edge browser to find out why this is not working. It's actually a security thing. And then one of the things that I like about Visual Studio 2019 is this process memory and all of my events that occurred so I could see my caching starting up. You can see calls to different parts of my application. I want to catch output anything that's done in my logging. I could also take a snapshot. See and then go and dig into what's happening in my memory right now. Well look at that. It turns out that I actually have almost 700 episodes of my podcast. So you'll notice that about a megabyte of memories being used up. You might think yourself why are you doing that Scott. Well I don't want to hit the database all the time. So in fact I've got instances instances look of v2 show right. Let's look at my extensions. I'm going to hit extensions manage extensions and see what I got here. I've got live share which lets me go and share my code but not my pixels with folks. I use the cloud explorer sometimes Visual Studio 2019 that lets me go and see what's going on in Azure because this application lives in Azure. So for example I can go over here click on cloud Explorer. Now I have my work account which I don't really use and I have my personal account. This one's my personal right here. I think I might want to actually filter these out because I really only care about my Visual Studio msdn account. So I'll turn these all off hit apply. So now I'm just going to see there we go. My local resources and my app services. You can see the app service plans that I've got for my blog and for my podcast. I've got a Linux one of Windows one. Here's one of the blogs. There's the main page. Here's Hanselman it's itself. What's cool about this is notice that I'm not even in the Azure portal. I can actually click files. Upload a file search files or directly see look. What's. Deployed which is really cool so I can right click and deploy and also go here and see log files and then do log streaming if I wanted to but if I wanted to see specific event logs or specific errors just double click on them. They'll download and put them inside of. Visual Studio for you which is pretty sweet. I tend to use big fonts. I think in this case I'm using Lucida console. I also like to control scroll a lot. I don't think that Visual Studio is going to say that I have any major issues. I'm noticing here in the health. Area that I don't think I have any code. That it calls out. But I could potentially do something like a refactoring here and reclit right click and say remove remove and sort usings. So that's my Visual Studio not super fancy pretty straightforward kind of a stock version of Visual Studio but it makes me happy. Be sure to send me your Visual Studio send me a screenshot. Do you have interesting fonts? Have you changed the custom colors? What extensions do you have going at me on Twitter s Hanselman and maybe going at Visual Studio as well. Thanks.