In this video, learn how to publish to Azure.
- [Instructor] Great, our project is up and running. Let's send it to Azure and take a look at what it looks like in the Cloud. Before we can do that, though, I need to open a browser and I need to go to portal.azure.com, and I need to create an Azure account with a pay-as-you-go subscription. Luckily for us I've already done that. So I'm going to log in to my Azure account, and enter my password. And if I see here I have no resources in this account, and this is just for development only. Returning to Visual Studio, I can control click or right click on a PC, and I can go down to publish, and I can say publish to Azure.
Now, the first time you do this this won't look like this in your project. It'll say log in with your username and password, which you saw me do just a second ago. So once you've created your page, you go subscription, you can log in and then you'll see the screen, and you can create a new app service, which is exactly what we're going to do. The app service name defaults to our project. In this case that's way too common a name for Azure. So we need to go something unique, so we're going to do iamsap-angular-azure. And you can see here the URL that's going to be used for this project. We're going to use my pay-as-you-go subscription, and I'm going to create a new resource group.
Resource groups are like folders of app services. So I'm going to call it iamsap-angular-azure. The standard naming convention in Azure is to put rg at the end of your resource group name. That way when you're looking at everything under your account it's easy to separate resource groups from actual applications. And I'm fine with the central US, but I am going to change the pricing tier to free. And this is never to be used for a production environment. This is purely for development. So we're talking the slowest possible, the least amount of resources, but it's free and for development free is fine with me.
So let's click create. And it tells us the server's going to take a little bit. And there it is, our application is deployed to Azure. Think about it. With just the use of the spa templates and a couple clicks in the publisher window, we have an app out running on the Cloud. I can refresh this app and see that it's up and it's running. It's not the fastest environment you've ever seen. But for development it's pretty good and it's going to work just fine. Now let's dive into some code and talk about something I'm really passionate about.
At the end of the course, you'll have skills to connect the popular Angular framework to key services in Microsoft ecosystem.
- Creating and configuring the Angular project
- Securing login
- Working with GitHub and Visual Studio Team Services
- Building APIs in .NET Core
- Securing .NET APIs
- Testing with Postman
- Building a .NET proxy from start to finish