. NET sites and applications differ, the site is dynamically executed without compiling, he relies only on his own documents, and even you can write JSP code directly in ASPX, In fact, the Web site can be said to be just open in the. NET platform, equivalent to the original Notepad encoding, he does not need to rely on. NET to execute (of course, if you reference. NET comes with a class library or tool is required), but the project needs to rely on the. NET platform.
New website today, found that the original new site there are two ways.
1. It has been used directly to create a new---website
Then add the project name after the solution is the name of the path
2. There is also a new--project, then choose web--New Asp.net.web
The project name is:
the difference between creating a new Web site and creating a new asp: VS2010 After SP1, there are two choices to make a new Web site project: Create a new Web site and create a new ASP. NET Web application. So what are the pros and cons of choosing "New Web Site" or "New ASP."? What should we choose?
On the Internet to check some information, a comparative summary, may be helpful to you. Now always use WebApplication way, feel more useful, suitable for relatively larger system. Website mode is "new site", more suitable for small and medium-sized enterprise website, the following specific introduction.
advantages of the WebApplication programming model：
The website compiles quickly, uses the increment compiles the pattern, only then the file is modified, this part only then will be the increment compiles in.
The generated assemblyThe difference between a new Web site and a new ASP. WebSite: Generate a random assembly name that requires a plug-in webdeployment to generate a single assembly WebApplication: You can specify that a Web site project generates a single assembly. Because it is a standalone assembly, you can specify the name of the application set, the version, the output location, and so on, as with other projects
You can split a site into multiple projects for easy management
You can exclude a file from your project and source code control
Easy to support VSTS Team Build for daily builds
More powerful code checking capabilities, and check policies are controlled by source code
You can do your own processing before and after compiling.
Resource Strong support for App_GlobalResources (online, not yet known)
Direct upgrade of large systems built using VS2003
Advantages of the website programming model：
Dynamically compile the page, you can see the effect immediately, without compiling the entire site (main advantage)
Same as above, can make the wrong part and the use of the part of the non-interference (can require only compiled through to check in)
You can generate an assembly per page (this is not typically the case)
You can use a directory as a Web application to process, directly copy files can be published, no project files (suitable for small sites)
The page can also be compiled into the assembly (should not be used, and webapplication can also be implemented through the Webdeployment plugin)
conversion of two programming models to each other：
the difference between a new Web site and a new ASP. VS2010 SP1 has a built-in translator that makes it easy to convert from website to WebApplication, just copy files and right-click "Convert to Web Application".
The difference between a new Web site and a new ASP. NET Web application is that there is no specific reverse conversion tool, but after comparison it is found that if the conversion is very simple, remove all *.designer.cs, *.aspx, *.ascx, *.master in the paging file Codebehind= "******.aspx.cs" is replaced in bulk with codefile= "******.aspx.cs" so that it can be converted back.
Differences between a new Web site and a new ASP. NET Web Application
