Differences between ASP. NET web applications and ASP. NET websites

WebapplicationAdvantages of the Programming Model:

● The website Compilation speed is fast and the incremental compilation mode is used. This part will be incrementally compiled only after the file is modified.

● GeneratedProgramSet
Website: generate a random Assembly name. You must use the plug-in webdeployment to generate a single assembly.
Webapplication: You can specify a website project to generate a single assembly. Because it is an independent assembly, you can specify the name, version, output location, and other information of the application assembly like other projects.

● The website can be split into multiple projects for convenient management

● It can be in and out of the projectSource codeExclude a file from management

● Easy support for vsts team build for daily build

● More powerfulCodeCheck function, and check policy is controlled by source code

● You can perform prescribed processing before and after compilation

 

WebsiteAdvantages of the Programming Model:

● Dynamically compile the page to see the effect immediately without compiling the entire site (main advantages)

● Same as above, this can make the error part irrelevant to the part used (it can be required that the part can be checked in only after compilation is passed)

● An assembly can be generated on each page (this method is not generally used)

● A directory can be processed as a web application, and files can be directly copied and published without project files (suitable for small sites)

● You can also compile the page into the assembly (it should not be used, and webapplication can also be implemented through the webdeployment plug-in)

 

There are also some differences and similarities:

All are designed for Web pages.

You can add ASP. NET folders.

The default. aspx web application displays two original files: default. aspx. CS and default. aspx. Designer. CS.

 

There is an original file default. aspx. CS.

There are two types of Web applications: re-emergence and release. One web site has only one publishing site.

There is no difference between a web application and a general winform in referencing namespaces;

 

After the web site is referenced, a bin folder contains DLL and PDB files.

Web applications can be referenced as class libraries, while Web websites cannot be referenced as class libraries.

For Web applications, you can add bin and app_code to the ASP. NET folder. For Web websites, you can add ASP. NET folders, Including bin and app_code.

You can also add components and classes for Web applications, but not for Web websites.

Although the source files are all default. aspx. CS, the Web application has a namespace and an additional system. Collections space reference is provided.

The Web application needs to be re-compiled after the underlying code of the page is modified, and the website does not need to be re-compiled.

You can add APS folders for websites, but not for Web applications.

A dll file is generated for a Web application project.

When the website is released, the DLL file is automatically generated, but the DLL file names are different each time.

Web applications have solutions and project files

 

The most obvious difference is that you have different deployment methods.

For applications, you only need the DLL files in the page and bin folder.

You also need to deploy the background file of the page

 

Relatively speaking, large websites are more suitable for Web application projects, while small websites are more suitable for web site projects.