Differences between APs. NET web applications and APs. Net websites

I have been engaged in. NET development for more than two years. One day, a new employee asked me: "APs. NET web applicationsProgramWhat is the difference with APS. Net websites ?". At that time, I was really stunned, because I didn't really care about this issue at ordinary times, because I have been using APs.. Net websites, whether in the MIS system or some websites, have not used APs.. NET web application. So today I checked:

Advantages of the webapplication programming model:

1. 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.

2. The generated Assembly: the difference between creating a website and creating an Asp.net web application. 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.

3. You can split your website into multiple projects to facilitate management.

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

5. Easy support for vsts team build for daily build

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

7. You can perform prescribed processing before and after compilation.

8. Strong resource support for app_globalresources (I have not learned about it on the Internet)

9. Directly upgrade a large system built using vs2003

Advantages of the website programming model:

1. dynamically compile the page to see the effect immediately without compiling the entire site (main advantages)

2. Same as above, it 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)

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

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

5. You can compile the page into a set of Programs (it should not be used, and webapplication can also be implemented through the webdeployment plug-in)