All language subtitles for 3. Default application files

When you create an to speed up net core embassy application, you could see that there were some default

files that came with the Temperley that we selected.

But what are these default files and what is their purpose?

So now let us go to Visual Studio and have a look at the default files that come with the MVC template

in Visual Studio.

The first option in here is the connected services.

And if you want to add a connected service, you can just right click in here.

Then go to the ADD Connected Service.

And then you can add services like the Open API, BGR, PC, etc..

Some other services are the Microsoft WCF and the authentication with Azure Active Directory.

Now, if you want to add a service dependency, you can just click here on the plus button.

And these are the options, like, for example, you can add the storage of misleader locally, you

can add a reference to the Azure storage, etc. So you can see in your a list of different services.

Now, I'll just close this window so by just clicking cancel.

Next, we have the dependencies and then inside the dependencies, you have the analysers and the frameworks.

Now, if I expand the frameworks inside here, you can see the ASP.NET Code app, and then you have

all the default dot net core libraries, like, for example, the anti forgery, the course, and then

don't you have, for example, the HDP, etc. And you also have the net core, that app.

The next year you have the properties and inside the properties folder, you have the launch settings

that jassam file.

And if you open these file, you'll have in the IRS settings.

So where the app is going to be run and the profiles.

Now you can have in your multiple profile.

So, for example, in this case, by default, we have two profiles.

The first one is the IRS Express and the second one is the E!

Tickets.

Now, inside the profiles, you can define common names and define the dotnet run messages.

The Longe browser, the application URL, which is the most important one, and also the environment

type.

Not when you create a profile in here, you'll be able to see the profile here on the dropdown.

So in this case, we have the IRS Express and the etiquettes.

So we have in here is Express and also the E tickets.

Now, if you create another profile, the profile will show up in here.

The next section is the root section.

And this is also known as the static file section, because inside here you normally keep the static

QSOs files, JavaScript files, custom libraries.

So, for example, if you open the leap folder in here, you are going to see the bootstrap, Jaqui,

etc. If you have, for example, static files that you want to use in your app, let's see some images

then you could create in here a separate images folder and then just stored the images in this section.

The next you have the controllers, the models and views.

And we have these folders because we selected the model view controller template as the default template.

So if you open the controller inside here we have the home controller.

And we said that the controllers are just c sharp classes that inherit from the base class controller.

In the models, you have the air view model, and that is by default the only model that we have in

here.

The next we have the views folder and interviews folder, we have the home folder and the shared folder.

Now, the reason why we have the home folder is because we have a HOONG controller.

And the way that the embassy works is that for each controller that you have in here, a test controller

for the controller, you will have a test folder in you.

And each views for the controller methods will be placed within that folder.

The shared folder is just a folder which has like the layout, the C sharp HDMI file, which is just

a razor view.

But this is the most important view in an ABC app, because in here you basically define how you want

to render your app.

So you would basically have the header we had, then you have the body and inside the body you have

another header for the navigation bar.

Then after the header, you have a div container.

And that inside this main tag, you have the render body.

Now, the render body in here is used to define what you want to render all your views.

So basically, the views that you have in your app, whenever you call a view or you navigate throughout

your app, there will all be rendered inside the div with the class container.

And then inside the main tag.

Then down here you have the filter.

And this has some default text.

And next, you are just loading some scripts.

And next in here, you have the underscore validation script, partial view.

And we are going to talk in the upcoming parts or departure views are.

So if you open this file inside, you will see that you have two references to two different G.K validation

related libraries.

And then the last view inside the shared folder is the air Dusti Sharp HD Amle.

And this is the default file that is used to render.

When you have an error, the next thing you have the view imports.

And we are going to talk about the view imports in the upcoming parts.

You have the view star.

And you can see here that you define as the default layout file to be the underscore layer.

See sharp HDMI file.

The next you have, the settings are do some file.

And this is also known as the configuration file, because in here you can store data like the connection

strings of the logging related configurations, etc..

The other file is a program Ducey's.

And this is known to be the entry point in all dotnet and bitartrate core applications, because it

has this main method.

And for the MVC apps, we have some pretty configurations like, for example, you need to use when

the app starts, these start up class.

And that brings us to the last class, which is the start of the series, which is also known as the

configuration class in the dot net core applications.

Now, inside this class, you have two main methods, the configure services and the configure method.

And as the predefined comments seen here, you need to configure services to add services to the container.

And we are talking about the default built in container in the Duffner core framework and use the configure

method to configure the HDP request pipeline.

Now, this is enough thiry in the upcoming parts, you'll start to create all the features one by one.