WEBVTT 00:01.440 --> 00:05.640 All right, more tools. This is Visual Studio, my favorite 00:06.140 --> 00:09.480 development environment. Why? Because it is very complete 00:09.980 --> 00:13.560 and it does a lot of work for me. In here I have a simple 00:14.060 --> 00:17.400 ASP. NET Core web application. What does that have to do 00:17.900 --> 00:21.600 with Azure? Well, I want to show you how an application works 00:22.100 --> 00:25.920 with Azure. This here uses an Azure SDK to talk with 00:26.420 --> 00:29.840 Azure storage Blobs here in Blob Container client class. 00:30.570 --> 00:34.250 This class comes from a NuGet package that is just a bunch of. 00:34.410 --> 00:36.810 NET classes that call the Azure APIs. 00:37.690 --> 00:41.450 There are many more SDKs like this, and Visual Studio 00:41.950 --> 00:44.650 itself also has native Azure capabilities. 00:45.450 --> 00:48.610 For instance, when I want to publish this app, I can 00:49.110 --> 00:52.690 choose to publish it to Azure. And when I do, I can choose 00:53.190 --> 00:56.810 where in Azure. I want this to go for instance to an Azure app, 00:57.310 --> 01:00.950 service web app and variations on that, or even a VM 01:01.450 --> 01:04.950 or container app. Cool. I can connect my 01:05.450 --> 01:08.550 Azure account to Visual Studio and enable it to access 01:08.630 --> 01:12.070 my resources like my app service web apps here. 01:12.870 --> 01:16.510 From here I can create resources as well, like a new web 01:17.010 --> 01:20.150 app, including a resource group and app service plan. 01:20.630 --> 01:24.470 I'll leave that for now. You get the point, right? Okay. 01:24.870 --> 01:29.740 Also I can integrate things into my apps by connecting services like 01:30.240 --> 01:33.300 this Application Insights for instance. Really handy. 01:34.020 --> 01:38.020 There are many other connections that I can make as well to services like these. 01:38.740 --> 01:42.100 And from here I can create these services on the spot 01:42.600 --> 01:46.300 or connect with existing ones. Cool. Let's move 01:46.800 --> 01:50.180 on to Visual Studio code. This is more lightweight editor and 01:50.680 --> 01:54.780 doesn't have all of these capabilities enabled by default. You need extensions 01:55.280 --> 01:57.620 to do that, like this Azure account extension. 01:58.430 --> 02:02.510 This enables this tab where I can see my Azure accounts. 02:03.150 --> 02:07.030 Here I can drill down to see my Azure resources like 02:07.530 --> 02:11.230 my storage accounts, for instance. And when I do drill down, 02:11.390 --> 02:15.430 I see that I need another extension. Each of these has 02:15.930 --> 02:19.630 its own extension. Needs its own SDKs to work 02:19.870 --> 02:23.070 like through this storage extension. Okay, 02:24.120 --> 02:27.480 now I can see my Blob containers and other storage accounts. 02:28.360 --> 02:31.480 Now I can use them. From here I can manage my 02:31.980 --> 02:34.760 storage like upload a file and do much more. 02:35.160 --> 02:39.120 Cool. The same goes for other service types like 02:39.620 --> 02:43.320 my app services. I can see them here, but I need this specific 02:43.820 --> 02:47.960 extension to work with them. This makes Visual Studio code so lightweight. 02:48.440 --> 02:51.960 Okay, Now I can use this web app. From Visual 02:52.460 --> 02:56.160 Studio code I can see everything, including application settings. 02:56.560 --> 02:59.840 And I can do things like start and stop the app as well, 03:00.000 --> 03:02.560 and also create and delete ones. 03:03.280 --> 03:06.720 Remember, all of this just talks with the Azure APIs 03:06.800 --> 03:09.200 that Azure resource Manager exposes.