Welcome back.

We've got our project created now, but having a website that you haven't seen

running in a browser, [INAUDIBLE] bad as useful as a book that you've never opened.

Luckily, Visual Studio makes it really easy.

Ready?

Let's do it.

To run a website, we'll click on the play button here at the top of the screen.

If you prefer to keep your hands on the keyboard, like I do,

you can also press the F5 function key.

But before we do that,

let's click the little down triangle here on the right hand side of the play button.

This displays a list of the installed browsers.

Using this list, we can select the browser that we want to use to run our website.

Let's select Google Chrome and then click the play button.

Visual Studio will build our website and load it into the browser that we selected.

Here's our website.

The first page that we see is our default page which for

our website is the homepage.

Using the menu here in the header, we can click on About,

to see the about page, or Contact to see the contact page.

If we click on Application Name, that takes us back to the homepage.

Let's switch back to Visual Studio.

Notice how our environment has changed, the output panel has been replaced

with the Autos and Call Stack panels, both of which are used for debugging.

Over here on the right, the Properties panel has been hidden and

we now have a Diagnostic Tools panel being displayed.

We're not gonna use the Diagnostic Tools during this workshop, so we can safely

collapse that panel by clicking the pin here in the right-hand corner.

There, to stop our application, click the stop button.

Our website has stopped running and

our environment returns back to what it was before.

Wasn't that fun?

I always enjoy seeing my websites running in a browser for the first time.

Whenever you start new website projects, it's helpful to get something up and

running as quickly as possible before you start making any other changes.

The process of making a small change or set a small changes then running your

website or application to review and test those changes, forms the basis

of what developers like to call iterative or incremental development.

Doing development in this way,

makes it easier to determine the source of a problem when something goes wrong.

Throughout your career as a developer, you'll literally do thousands and

thousands of iterations.

For our next iteration,

let's take a closer look at the folder structure of our project.