There are two modes of VS Web development:
1. Website mode 2, Application Modewhere the site mode is released, consider checking "use fixed named and single-page assemblies"Such as
website mode:
Site mode for new site
Site mode for new Web site second step
Application Mode:
New app Site mode
New app Site Mode second step
The difference between the two:
1, whether to compile:(1) Web content changes do not need to compile (2) the site mode of CS code changes, do not need to compile, refresh to see the effect (3) Apply the site mode of CS code changes, need to compile the system, to see the effect(personal feeling, site mode content modified after the page can be seen to see the effect, high development efficiency)
2. page file:(1) Website mode: There are two files: aspx and Aspx.cs (2) App website: There are three files: aspx, Aspx.cs and. Aspx.designer.cs
3. Website release:(1) Website mode: 2 kinds of a.aspx and Aspx.cs are released to run, the direct effective mode B. Use vs Package release mode (2) Apply website: 1 way after compiling, CS becomes a unified DLL file, publish aspx and other paging files and DLLs up, CS file does not need to be published.
4, the website mode of the website publishing special instructions:If you choose the mode that the CS file is published on, there is no special indication if the VS packaged release mode, note an option:
Site Mode Publishing Site
Site posting check using fixed-named and single-page assemblies
such as
If you do not tick "use fixed named and single-page assemblies"The published DLL will be randomly named, page inherits will update the DLL's random name as follows source code:
<%@ Page Language="C #"AutoEventWireup="true"Inherits="Errorpage_urlerror, App_web_iixanlav" %><!DOCTYPE HTML Public "-//W3C//DTD XHTML 1.0 transitional//en" "http://www.w3.org/TR/xhtml1/DTD/ Xhtml1-transitional.dtd "><HTMLxmlns= "http://www.w3.org/1999/xhtml"><HeadID= "Head1"runat= "Server"><title>403 pages</title><styletype= "Text/css">. Btnback{Top:476px;position:Absolute;text-align:Center;width:100%;}</style></Head><Bodystyle= "text-align:center; margin:0px;"><imgID= "Error_img"src=".. /images/error/405.png " /><formID= "Form1"runat= "Server"><Divclass= "Btnback"><inputID= "Button1"type= "button"style= "width:130px; Height:50px;background:url" (.. /images/error/error_back.png) No-repeat; Border:none; Color: #f00; Cursor:pointer; "onclick= "javascript:window.location=". /login.aspx '; " /></Div> <Div> <asp:literalID= "Ltmessage"runat= "Server"></asp:literal> </Div></form></Body></HTML>
The App_web_iixanlav in the above inherits= "Errorpage_urlerror, App_web_iixanlav" will vary depending on the compiled DLL.(Note: In this case, the bin directory does not empty, the bin directory will accumulate the history of different versions of the DLL files, the bin will become bloated)
If you tick "use fixed named and single-page assemblies"Published DLLs will be fixed named, page inherits also in the two release version also consistent with the following source code:
<%@ Page Language="C #"AutoEventWireup="true"Inherits="Errorpage_urlerror, App_web_urlerror.aspx.83c043b9" %><!DOCTYPE HTML Public "-//W3C//DTD XHTML 1.0 transitional//en" "http://www.w3.org/TR/xhtml1/DTD/ Xhtml1-transitional.dtd "><HTMLxmlns= "http://www.w3.org/1999/xhtml"><HeadID= "Head1"runat= "Server"><title>403 pages</title><styletype= "Text/css">. Btnback{Top:476px;position:Absolute;text-align:Center;width:100%;}</style></Head><Bodystyle= "text-align:center; margin:0px;"><imgID= "Error_img"src=".. /images/error/405.png " /><formID= "Form1"runat= "Server"><Divclass= "Btnback"><inputID= "Button1"type= "button"style= "width:130px; Height:50px;background:url" (.. /images/error/error_back.png) No-repeat; Border:none; Color: #f00; Cursor:pointer; "onclick= "javascript:window.location=". /login.aspx '; " /></Div> <Div> <asp:literalID= "Ltmessage"runat= "Server"></asp:literal> </Div></form></Body></HTML>
Original link:
Http://www.lookdaima.com/WebForms/WebPages/Blanks/Pm/Docs/DocItemDetail.aspx?id=ea2fd50d-ca48-47d0-a09c-02d3736bc5dd
vs. Web site development Release deployment different scenarios description