Skip to main content

ASP.NET MVC : Folder structure of ASP.NET MVC application

So we have learned the basics of ASP.Net MVC, now before start using it in our application, let's have a look at the folder structure of a typical ASP.NET MVC.

The MVC framework is based on default naming and the folder names are equal in all MVC applications. Controllers are in the Controllers folder, Views are in the Views folder, and Models are in the Models folder. This standard naming reduces the amount of code and makes it easier for developers to understand MVC projects.

Folder structure of MVC3 Application

A typical ASP.NET MVC web application has the following folder content:

Application information
•      Properties
•      References
Application folders
•      App_Data Folder
•      Content Folder
•      Controllers Folder
•      Models Folder
•      Views Folder
•      Scripts Folder
Configuration files
•      Global.asax
•      Web.config

Properties: Contains Application properties, i.e. AssemblyInfo.cs

References: All the default application references, we can add more references if we need.

The App_Data Folder: The App_Data folder is for storing application data. For example SQL database or SQL scripts.

The Content Folder: This folder is used for static files like style sheets (CSS files), Themes, icons, and images, etc. When you create a new project Visual Web Developer adds a standard style sheet file (Site.css file under this folder) to the project.

The Controllers Folder: The Controllers folder contains the controller classes responsible for handling user input and responses. MVC requires the name of all controller files to end with "Controller". For example “HelloWorldController”.

The Models Folder: The Models folder contains the classes that represent the application models. Models hold and manipulate application data.

The Views Folder: This folder stores the files related to the display of the application (UI). Whenever you create a new project Visual Web Developer adds a new folder (“Shared folder” under Views folder). This Shared folder is used to store views shared between controllers (master pages and layout pages). The Views folder contains one folder for each controller.

The following file types can be found in the Views Folder:

File Type
Extention
Plain HTML
.htm or .html
Classic ASP
.asp
Classic ASP.NET
.aspx
ASP.NET Razor C#
.cshtml
ASP.NET Razor VB
.vbhtml

The Scripts Folder: The Scripts folder stores the JavaScript/jQuery files of the application. By default Visual Web Developer fills this folder with standard MVC, Ajax, and jQuery files.
Default script files

Global.asax: Contains Global settings of Application, by default it contains “RegisterRoutes” and “Application_Start” methods under the “MvcApplication” class.

Web.config: It contains all the configuration-related information of the application (This is the same as we do have in the ASP.NET web application).
Labels:

Comments

Post a Comment

Popular posts from this blog

Error 405 : ASP.NET Core Web API PUT and DELETE Methods not allowed

Recently, while working with .Net core API I came across the issue of “Error 405 — Methods not Allowed” After some research, I found out that both GET and POST requests working fine but neither PUT nor DELETE requests working. Another thing is that the PUT and DELETE request was also working fine on my local machine but failed when we host on our Azure server. When I explored the issue on the web it led me to the conclusion that WebDAVModule seems to set PUT and DELETE request methods disabled by default and due to that PUT and DELETE throw 405 errors. To make the PUT and DELETE requests work, we need to override the WebDAVModule setting in web.config file by adding the below settings under “ system.webServer ”. < system.webServer >   < modules runAllManagedModulesForAllRequests = " false " >     < remove name = " WebDAVModule " />   </ modules > </ system.webServer > There may be 2 web.config files in y...
Post a Comment
Read more

C#: Merging Excel cells with NPOI HSSFWorkbook

In this post we’ll see how to merge the two or more cell with each other while creating the excel sheet using NPOI . Mentioned below is code to merge multiple cells, in this example we are merging first cell to fifth cell of first row (you can adjust row or cell range by passing particular parameters in CellRangeAddress). //Created new Workbook var hwb = new NPOI.HSSF.UserModel. HSSFWorkbook (); //Create worksheet with name. var sheet = hwb.CreateSheet( "new sheet" ); //Create row and cell. var row = sheet.CreateRow(0); var cell = row.CreateCell(0); ; //Set text inside cell cell.SetCellValue( "This is Merged cell" ); cell.CellStyle.WrapText = true ; //define cell range address // parameters: -> first row to last and first cell to last cell var cra = new NPOI.SS.Util. CellRangeAddress (0, 0, 0, 4); //Add merged region to sheet. sheet.AddMergedRegion(cra); Hope this solution helps you J
4 comments
Read more

How to set Swagger as the default start page for API hosted on the Azure web app?

I created an Asp.Net Core 2.x Web API and configured Swagger on it, below is the code added in Configure method under Startup.cs file, for full swagger configuration, check here //Add swagger configuration app.UseSwagger(); app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" ); }); On my local machine when I run the API it is automatically redirected to the Swagger page. However, when I hosted this API as an Azure web app it is not redirecting directly to the Swagger and to access the swagger, I had to append /swagger in the URL, for example, https://testapi.azurewebsites.net/swagger/ Solution: Set RoutePrefix to string.Empty under app.UseSwaggerUI like below: app.UseSwaggerUI(c => {     c.SwaggerEndpoint( "../swagger/v1/swagger.json" , "Test API V1" );      c.RoutePrefix = string .Empty; // Set Swagger UI at apps root }); And that’s it, now when you b...
Post a Comment
Read more