Join Kevin Ford for an in-depth discussion in this video The VSAC web portal, part of Visual Studio App Center for Developers.
- [Instructor] Let's take a quick tour of the Visual Studio App Center web portal. We're going to click on the Get Started link to either create a new account or use an existing one. As you can see, there are a wide variety of account types we can use for this. For me, I'm going to use my existing Google account and log in. Since Chrome already has my user name and password, I don't have to enter them in the browser. If the browser does not have your information, you may have to log in with your account.
Let's take a look at the account settings and we'll do that by clicking on the actual user and go to Account Settings. Here we can see some interesting things. Profile and password are what we'd expect, but the section under Billing is interesting. To start with, we can have one build agent running concurrently. We can add more build agents at $40 per month each. We also get 90 free days of using the testing service. After that, it's $99 per month.
There also is an upcoming feature to allow you to communicate with users of your application. Let's take a look under the Azure section, so I'm going to click on Azure there. From here, we can attach an account. You may want to attach an Azure account if you want to do some of these purchase services such as using the testing service. I'm going to click Add subscription, and I'll pick an account that I already have tied into Azure. If you do not currently have an Azure account, you should stop now and set one up. You will need it to finish this section.
I'm going to select my Visual Studio Premium MSDN subscription for this, and press Connect. Now we have an Azure subscription attached, and we can use it to purchase some of those premium services. Let's take a look at another VSAC account I have, that already has some organizations created and also apps created. This is an example of a portal that's already in use. On the left hand side, we can see that there's a hamburger menu that can be used to collapse and reopen the left hand screen.
Also, under our account name, we can also see any organizations that have been set up. In the main area of the screen, we will see a list of applications that we've set up. If we use this same account to log into VSAC, as we used into an existing HockeyApp account, any apps that were there would show up here too. An app represents a single application for a single platform. That is to say, if we have an application that runs in Android and iOS, we would have to set up two applications in VSAC.
This is true if we're using Objective C, Android Java, Xamarin, React Native, etc. In the top right of the screen, we can switch back and forth in our view style from a tile view to a list view. I personally like the list view, so we're going to leave it right there. We also have the ability to filter our applications by platform. This can be helpful as your list of applications grows longer. Finally, in the upper right, we have an option to create a new team or application. We will be looking at these functions in the next chapter.
- Adding applications to the VSAC
- Using custom build scripts
- Creating iOS and Android builds
- Creating UI tests
- Automating tests
- Distributing apps
- Examining crash logs and analytics
- Adding push notifications
- Using CodePush for deployments