[MUSIC]
>> Hello, my name is Jeremy Likness.
I'm a Cloud Developer Advocate with Microsoft.
We're here to take you through a QuickStart in
the Azure DevCenter for .NET. I'm here with.
>> My name is Scott Cate,
also Cloud Developer Advocate,
and we've been working on these QuickStarts,
which should make it really simple for you to follow
along and jump right into Azure with your .NET code.
>> Exactly. We're going to get started with one of
the QuickStarts that are on
the site and we'll share the link with you.
Scott, what's the first step for this?
>> The first step is create a brand new
ASP.NET MVC application and deploy it to Azure.
>> Great, let's show them what that looks like.
>> On my machine, if I jump into Visual Studio,
I've already opened Visual Studio
2017 and under the File-New-Project,
I'm selecting Cloud ASP.NET application.
I've already given it a name of DevCentered QuickStart deploy.
I'll simply click "Okay",
and that's going to take just a moment to
create my MVC application.
Now without making any code changes,
we're simply going to publish this straight up to Azure.
>> The QuickStart will tell you exactly which
workloads you need to get these templates into your system.
There's an ASP.NET for web development and an Azure SDK,
so he set that up in Visual Studio and that
takes him right to the templates that are ready to publish.
>> That's right. Now if we right click
"Publish" on the Project File,
you'll see I have a Publish menu,
it's going to ask where I want to publish?
We'll select "Azure",
simply click "Publish",
it will give us a unique name.
You'll see this timestamp at the end of
my project name that will actually become a portion of the URL,
and now I can simply click "Create".
>> When it's creating,
it's actually spinning up an Azure Web Service,
which is a very cool platform as a service offering that gives you
a lot of flexibility around how you scale
your web app and some elasticity.
There's a lot of control there and it comes
right out of the box with this template.
>> Now that my application has been deployed,
it'll take just a moment to get started,
the first time it's deployed it has to actually warm up the slot,
so this usually takes about 10 seconds.
You'll notice the URL that's created is
my project name plus that timestamp that we saw,
and then it just gives us a default address
of dot azurewebsites.net.
Now, once this is deployed,
so here we go, we can see my app is running.
What I'd like to now do is update the application.
I'll flip back to Visual Studio and I'll Open
the Home view of the index page.
I'll just zoom into this so you can see it a little bit better,
and under "Getting Started",
let's just say getting started with deployment.
I can actually publish a couple of different places,
I can go back to the project and right-click "Publish",
the publish engine is smart
enough to know only to deploy the files that were changed.
I can also right-click on the file itself and publish,
or there's a keyboard shortcut of alt semicolon p,
so I click over here,
"Alt semicolon P", you'll see that
that will publish just that file.
It's pretty quick, and since my application is already warmed up,
I can come back here and refresh.
You'll see that takes just a second and my
"Getting Started" will be
replaced with getting started with deployment copy that we fixed.
Just like that, we've taken a couple of minutes
and walked through the QuickStart,
and in about two to three to four minutes,
we were able to create a new app,
deploy it to Azure,
make a change, and then deploy
that change to Azure websites as well.
>> All of these Quick Starts are on the DevCenter,
this is a simple straightforward example.
We have everything from connecting to
relational databases in Cosmos DB,
so you'll want to check that out
and get up and running within minutes.
>> Thanks.