>>Hey friends. I’m here with Barry Luijbregts, AzureBarry on Twitter. You should follow him, Twitter.com/AzureBarry. Barry is one of our first people to come in Azure Friday and he works at Microsoft, and this is important because I want you to keep it real. I want you to talk to me about Azure for.NET Developers, because you’re not selling anything, you now work at Microsoft.>>Exactly. Yeah.>>So you’ve also put together a free ebook that we can check out. And we made a small URL for you. So, aka.ms/azurefordotnetdevs, and you really are focusing on Azure from a.NET Developer’s perspective?>>Exactly, yeah. So, this is a free ebook that I co-wrote with a bunch of Microsoft employees, and it explains why Azure is cool for dotnetdevs, and how you can get started. So, this is cool for.NET Developers that are new to Azure, but also for.NET Developers that already are familiar with Azure but just want to know which services are out for me as dotnetdev and which tools can I actually use.>>Yeah. There’s a lot to choose from and sometimes it’s overwhelming. Sometimes people say, well, Azure.Net people should use only app service.>>Exactly.>>There’s a lot of choices out there, it’s hard to make this decision.>>Exactly, yeah. So, in the book, we actually cover a couple of things. We cover what can Azure do for you, as a.NET Developer. And then we cover a bunch of services, so it’s kind of a service catalog. Like you said, app services but also things like CDN, which are very useful containers, all that stuff for running your applications in.Net or in Azure. Things for storing data in Azure, securing your.Net application in Azure, and all the Azure services like Media Services, IoT Anche, IoT Hub, there are many many services, that’s all listed in here. And more importantly there’s also a section about tools that you can use for developing, debugging, and troubleshooting. Good.Net applications in Azure.>>So, do you think this book is a kind of a decision tree to make the right decision for your application, because everyone’s application is different?>>Yeah. It also contains stable’s, where you can see, what do I want to use for running my application. Which one. Which services are the best picks for me. So you can just use that to pick the best services for you.>>Okay. Azure for some beginner.Net devs is just putting a website up.>>Yeah exactly.>>And for some older.Net devs, and by older I mean they’ve been in the business for a long time perhaps they will take a single server and they’ll get IRS and they’ll talk to each other. But to have real true Cloud Scale, there’s techniques and things that you can do to make your application scale both horizontally and vertically.>>Exactly. And you can do that very basically, with a slider you can scale up and down, or you can do it much more advanced as well, with automatic scaling and all that stuff.>>Right. Things like surface fabric and other things we’ve talked about on on the show. And now when I get visual studio, do I have all the tools that I need to be a dotnet developer in Azure?>>Not yet per say, and I want to show you how to get those tools. So if it was visual studio 2017, let me show you that here. When you go to tools, and get tools and features, you actually go to the visual studio installer, and here you see all the workloads that visual studio can run.>>It’s is a good reminder you can run the installer multiple times.>>Exactly. And is actually very quick in visual studio 2017.>>That’s nice to know.>>Yes. So you can have workloads for.Net Desktop development for instance but also for Azure, and it’s this one here. And when you click on this and you install this, you get all sorts of features in visual studio to work with Azure very easily.>>So our workload is the word for that box that then installs a number of features?>>Exactly.>>So that’s for Visual studio 2017. But if you’re running Visual studio 2015 for instance, you can also download the SDK on this page here, and onto tools to work with for instance Azure functions or Azure Cosmos DB, there’s a local emulator all that stuff.>>That’s cool. That’s nice to know that people on a different version of Visual Studio aren’t left behind.>>Exactly. So when you actually have this workload installed in Visual studio 2017, you get a bunch of things.>>Okay.>>So first of all, when you do file a new project, you get a new category that’s called Cloud. And as you see here, you get to start to as your functions for instance, a project as your Cloud services resource groups, and all sorts of things for the Cloud out of the books. It’s very easy. And, you also get the ability to publish things to the Cloud very easily. So for instance, I have here ASP.Net Core application. Very simple one. And now one because I have the workload installed, I can just right click on the project, and I say publish, and then I can pick Microsoft Azure app services for instance, and then I can just publish it today. And from here, I can create new app service if I want to, whether a new resource group and a new service plan. I don’t have to go to the Azure portal. I do all of that just from here, From Visual Studio, and it’s very powerful.>>So people who already have Visual Studio 2017 on their machine, but maybe haven’t kind of dipped their toe into Azure yet just need to go and run the installer again or go to the tools menu and take it features. They can add this and now these will light up in different places within Visual Studio.>>Exactly. Yes. So it’s very easy to do. And you get the very powerful features like for instance this publishing to Azure and creating an app service from scratch there. So, I’ve actually already published this application in Azure, and once you’ve done that, you get something like this within.Azure websites.Net extension, and has this website that we see here. We’re going to play with that later. Another thing that you get out of the books is that the Cloud Explorer. And it’s this little thing here. And this allows you to see all the services that you have in Azure, and to examine them and to work with them. Like for instance, the storage account here, I can just drill down into it, and actually work with it and see my Blob’s. There are other tools for that as well, like the Azure Storage Explorer, but when you have this workload enabled you can just do it from Visual Studio, and that’s very cool. And like I said, I’ve already published this application to Azure. So, here we can see it. It’s Web application with a big number behind it. And from here, I can do things like actually stop it, or see the streaming logs, or attach a debugger, and just debug the whole thing from here. That’s very cool.>>So you can do all of that within Visual Studio, is the intent to keep you out of the Azure portal or just that you just don’t need to go up there much because you’re living in Visual Studio anyway?>>It’s not per say the intent to not keep you out of that portal, but just to have everything at your fingertips in Visual Studio because you are living in there anyways, you’re there anyways so, why leave and disrupt your productivity.>>Very cool.>>So another thing that you also get is the Local Storage account that comes with the Azure workload, and you see that here. This is actually a storage emulated. It runs locally on my machine. I can just use that just like I use Azure’s storage that’s actually in Azure.>>Okay. So I could be writing and ask an application that talks to Azure storage and I could be doing on an airplane because I have my own local version of Azure storage.>>Exactly. And there are lots more local tools like the Runtime for Azure functions for instance.>>Yeah.>>There are Cosmos DB local emulator, and more coming like service fabric is already there. So those things you can use to do local development on Azure when you’re on a plane for instance.>>Very cool.>>So it is very cool. So, like I said, you can also debug things from here. So things that are actually running in the Cloud you can just click “Debug” and then you attach the debugger to here. And one very cool feature there, is that you can attach the Snapshot Debugger. And what that is, is that it allows you to debug something that is actually running in production without stopping it.>>I see. Because if you attached the debugger to something that everyone stops all threats stop, we’re now debugging, and you would never want to do that in production.>>Exactly. Because then your application is passed, and then your users have a problem, and you don’t want that.>>So, this application here, I can now just debugged it in production, and I actually have the Snapchat debugger already attached to it. And that’s what you see here. This is the Snapchat debugger in practice. And if you look at this code here, you see that I’m doing a couple of things here about the action of the controller, I just have a count that says you are visitor number count, and then it just shows that.>>I see.>>But when I’ve done that, when I’ve actually hit this about page, you can see that here. I can just continue with my application.>>So the application is still live and in production?>>Yeah. But I also have a snapshot that is now collected, because I’ve actually hit that thing. So it’s a bit different and a break point. Snapchat is just, what it sounds like, a snapshot of the application at a certain point in time where the breakpoints used to be.>>Alright. Feels like debugging, because it is debugging. You’ve got your local, you’re not in a break point, you are at snap point, and then at this point you see across there like really what’s going on in production.>>Exactly.>>This is great for those experiences where I don’t know why it works this way, but it’s working differently in production than it is on my local machine.>>Exactly. Plus you have the full debug experience that you have when you’re debugging, but now with the production app still running, and this is available only for.Net applications. So this is very powerful for.Net developers that are using Azure.>>Yes, so.Net people Azure is a natural extension for what they’re used to doing. You’ve got all these visual studio tools and then you’ve got benefits that other languages and other platforms don’t have like being with you snapshot debugging.>>Exactly. So, tools like these and other tools like the function local tools, Cosmos DB emulator, and all sorts of other tools in Visual Studio, are the things we describe in that free Ebook that you can download it.>>Maybe you could bring up that URL one more time. Well check it out. That was aka.ms/Azurefordotnetdevs spell that out dotnetdevs. That’s a free eBook. We can check out and people can follow you @AzureBarry on Twitter.>>Exactly.>>Fantastic. I am learning all about how Azure makes.Net devs that much better here on Azure Friday.