Hi All,
In ASP.NET 5 Microsoft targeted to change the solution folder structure. Here is the sample solution structure.
The first thing you may notice about this new structure is that it includes a Solution Items folder with a global.json file, and the web project itself is located within a src folder within the solution. The new structure also includes a special wwwroot folder and a Dependencies section in addition to the References section that was present in past versions of ASP.NET (but which has been updated in this version). In the root the project there are also several new files such as bower.json, appsettings.json, gulpfile.js, package.json, project.json, and Startup.cs. You may notice that the filesglobal.asax, packages.config, and web.config are gone. In previous versions of ASP.NET, a great deal of application configuration was stored in these files and in the project file. In ASP.NET 5, this information and logic has been refactored into files that are generally smaller and more focused.
global.json file
The global.json file is used to configure the solution as a whole. It includes just two sections, projects and sdk by default.
The projects property designates which folders contain source code for the solution. By default the project structure places source files in a src folder, allowing build artifacts to be placed in a sibling folder, making it easier to exclude such things from source control.
The sdk property specifies the version of the DNX (.Net Execution Environment) that Visual Studio will use when opening the solution. It’s set here, rather than in project.json, to avoid scenarios where different projects within a solution are targeting different versions of the SDK
Dependencies
Now MSDN maintaining client side and server side dependencies/references as a separate folders
Dependencies folder : This will be used to maintain client side dependencies with the help of bower and node.js
References will have server side dependencies
bower.json : Client side packages/dependencies configuration file. It works with bower (a client side framework manager)
wwwroot : It contains the static files like images, scripts etc
In ASP.NET 5 Microsoft targeted to change the solution folder structure. Here is the sample solution structure.
The first thing you may notice about this new structure is that it includes a Solution Items folder with a global.json file, and the web project itself is located within a src folder within the solution. The new structure also includes a special wwwroot folder and a Dependencies section in addition to the References section that was present in past versions of ASP.NET (but which has been updated in this version). In the root the project there are also several new files such as bower.json, appsettings.json, gulpfile.js, package.json, project.json, and Startup.cs. You may notice that the files
global.json file
The global.json file is used to configure the solution as a whole. It includes just two sections, projects and sdk by default.
The projects property designates which folders contain source code for the solution. By default the project structure places source files in a src folder, allowing build artifacts to be placed in a sibling folder, making it easier to exclude such things from source control.
The sdk property specifies the version of the DNX (.Net Execution Environment) that Visual Studio will use when opening the solution. It’s set here, rather than in project.json, to avoid scenarios where different projects within a solution are targeting different versions of the SDK
Dependencies
Now MSDN maintaining client side and server side dependencies/references as a separate folders
Dependencies folder : This will be used to maintain client side dependencies with the help of bower and node.js
References will have server side dependencies
bower.json : Client side packages/dependencies configuration file. It works with bower (a client side framework manager)
wwwroot : It contains the static files like images, scripts etc