物業(yè)管理系統(tǒng)外文翻譯

1、<p><b>　　外 文 翻 譯</b></p><p>　　畢業(yè)設(shè)計題目： 基于ASP.NET的 </p><p>　　物業(yè)管理系統(tǒng)開發(fā) </p><p>　　原文1： ASP.NET 2.0 Web Pages </p><p>　　and Web Contr

2、ols </p><p>　　譯文1： ASP.NET 2.0 網(wǎng)頁和Web控件 </p><p>　　原文2：The Role of Global.asax File</p><p>　　譯文2： Global.asax文件的作用 </p><p><b>　　原文1</b>&

3、lt;/p><p>　　ASP.NET 2.0 Web Pages and Web Controls</p><p>　　Until now, all of the example applications in this text have focused on console-based and Windows Forms front ends. In this chapter and t

4、he next, you’ll explore how the .NET platform facilitates the construction of browser-based presentation layers. To begin, you’ll quickly review a number of key web-centric concepts (HTTP, HTML, client-side, and server-s

5、ide script) and the role of the web server (including the ASP.NET development server, WebDev.WebServer.exe).</p><p>　　With this web primer out of the way, the remainder of this chapter concentrates on the co

6、mposition of ASP.NET (including the enhanced code-behind model) and how to work with ASP.NET web controls. As you will see, ASP.NET 2.0 provides a number of new web controls, a new “master page”model, and various customi

7、zation techniques.</p><p>　　The Role of HTTP</p><p>　　Web applications are very different animals from traditional desktop applications (to say the least).The first obvious difference is that a

8、production-level web application will always involve at least two networked machines (of course, during development it is entirely possible to have a single machine play the role of both client and server). Given this fa

9、ct, the machines in question must agree upon a particular wire protocol to determine how to send and receive data. The wire protocol that co</p><p>　　When a client machine launches a web browser (such as Net

10、scape Navigator, Mozilla Firefox,or Microsoft Internet Explorer), an HTTP request is made to access a particular resource (such as an *.aspx or *.htm file) on the remote server machine. HTTP is a text-based protocol that

11、 is built upon a standard request/response paradigm. For example, if you navigate to www. IntertechTraining.com, the browser software leverages a web technology termed Domain Name Service (DNS) that converts the register

12、ed </p><p>　　Once the hosting web server receives the incoming HTTP request, the specified resource may contain logic that scrapes out any client-supplied input values (such as values within a text box) in o

13、rder to format a proper HTTP response. Web programmers may leverage any number of technologies</p><p>　　(CGI, ASP, ASP.NET, Java servlets, etc.) to dynamically generate the content to be emitted into the HTT

14、P response. At this point, the client-side browser renders the HTML emitted from the web server. </p><p>　　Another aspect of web development that is markedly different from traditional desktop programming is

15、 the fact that HTTP is an essentially stateless wire protocol. As soon as the web server emits a response to the client, everything about the previous interaction is forgotten. Therefore, as a web developer, it is up to

16、you take specific steps to “remember” information (such as items in a shopping cart) about the clients who are currently logged on to your site. As you will see in the next chapter</p><p>　　Understanding Web

17、 Applications and Web Servers</p><p>　　A web application can be understood as a collection of files (*.htm, *.asp, *.aspx, image files, etc.) and related components (such as a .NET code library) stored withi

18、n a particular set of directories on a given web server. As shown in Chapter 24, web applications have a specific life cycle and provide numerous events (such as initial startup or final shutdown) that you can hook into.

19、</p><p>　　A web server is a software product in charge of hosting your web applications, and it typically provides a number of related services such as integrated security, File Transfer Protocol (FTP) suppo

20、rt, mail exchange services, and so forth. Internet Information Server (IIS) is Microsoft’s enterprise-level web server product, and as you would guess, it has intrinsic support for classic ASP as well as ASP.NET web appl

21、ications.</p><p>　　When you build ASP.NET web applications, you will often need to interact with IIS. Be aware, however, that IIS is not automatically selected when you install the Windows Server 2003 or Win

22、dows XP Professional Edition (you can’t install IIS on the Home editions of Windows). Therefore, depending on the configuration of your development machine, you may be required to manually install IIS before proceeding t

23、hrough this chapter. To do so, simply access the Add/Remove Program applet from the Control </p><p>　　Working with IIS Virtual Directories</p><p>　　A single IIS installation is able to host nume

24、rous web applications, each of which resides in a virtual directory. Each virtual directory is mapped to a physical directory on the local hard drive. Therefore, if you create a new virtual directory named CarsRUs, the o

25、utside world can navigate to this site using a URL such as http://www.CarsRUs.com (assuming your site’s IP address has been registered with the world at large). Under the hood, the virtual directory maps to a physical ro

26、ot directory s</p><p>　　When you create ASP.NET web applications using Visual Studio 2005, you have the option of generating a new virtual directory for the current website. However, you are also able to man

27、ually create a virtual directory by hand. For the sake of illustration, assume you wish to create a simple web application named Cars. The first step is to create a new folder on your machine to hold the collection of fi

28、les that constitute this new site (e.g., C:\CodeTests\CarsWebSite).</p><p>　　Next, you need to create a new virtual directory to host the Cars site. Simply right-click the Default Web Site node of IIS and se

29、lect New ?Virtual Directory from the context menu. This menu selection launches an integrated wizard. Skip past the welcome screen and give your website a name (Cars). Next, you are asked to specify the physical folder o

30、n your hard drive that contains the various files and images that represent this site (in this case, C:\CodeTests\CarsWebSite).</p><p>　　The final step of the wizard prompts you for some basic traits about y

31、our new virtual directory (such as read/write access to the files it contains, the ability to view these files from a web browser, the ability to launch executables [e.g., CGI applications], etc.). For this example, the

32、default selections are just fine (be aware that you can always modify your selections after running this tool using various right-click Property dialog boxes integrated within IIS).</p><p><b>　　譯文1<

33、/b></p><p><b>　　作者：迪諾·弗雷</b></p><p><b>　　國籍：美國</b></p><p>　　出處：ASP.NET 2.0 and Data-Bound Controls</p><p>　　ASP.NET 2.0網(wǎng)頁和Web控件</p>

34、;<p>　　到現(xiàn)在為止，本書的示例應(yīng)用程序主要集中在控制臺和基于Windows窗體前端。在本章及下面學(xué)習(xí)中，將探討如何用.NET平臺促進瀏覽器的建設(shè)。首先，你很快就會再次看到關(guān)于網(wǎng)絡(luò)中心的概念（HTTP，HTML格式，客戶端和服務(wù)器端腳本）和web服務(wù)器（包括ASP.NET開發(fā)服務(wù)器，WebDev.WebServer作用。exe文件）。</p><p>　　了這一點，本章的剩余部分主要是ASP網(wǎng)絡(luò)

35、（包括增強的代碼隱藏模型），以及如何使用ASP.NET Web控件和ASP.NET組成。正如你所看到的，ASP.NET 2.0提供了一些新的網(wǎng)絡(luò)控制模式，新的“母版頁”的模式，以及各種定制技術(shù)。</p><p><b>　　HTTP的作用</b></p><p>　　Web應(yīng)用程序不同于傳統(tǒng)的桌面應(yīng)用程序。第一個明顯不同的是，產(chǎn)生Web應(yīng)用程序?qū)⒅辽偕婕皟膳_聯(lián)網(wǎng)的機器

36、（當(dāng)然在開發(fā)過程中完全有可能有一臺機器扮演客戶端和服務(wù)器角色）。鑒于這一事實，機器必須確定一個特定的有線協(xié)議，以確定如何發(fā)送和接收數(shù)據(jù)。線路協(xié)議,關(guān)系到計算機的問題是超文本傳遞協(xié)議（HTTP）。</p><p>　　當(dāng)客戶機啟動一個（如Netscape Navigator，Mozilla Firefox瀏覽器，或Microsoft Internet Explorer）瀏覽器，一個HTTP請求訪問（如*. aspx

37、或*. htm文件）在遠程服務(wù)器上的特定資源。 HTTP是一個基于文本的協(xié)議，是建立在一個標(biāo)準(zhǔn)的請求/響應(yīng)式。例如，如果導(dǎo)航到http://www.IntertechTraining.com，瀏覽器軟件利用網(wǎng)絡(luò)技術(shù)網(wǎng)域名稱服務(wù)（DNS）轉(zhuǎn)換成由四個部分組成，32位數(shù)值（又名IP地址）注冊的網(wǎng)址。此時，瀏覽器打開一個（通常是通過端口80）套接字連接和發(fā)送的默認(rèn)HTTP網(wǎng)頁上http://www.IntertechTraining.com要

38、求。</p><p>　　一旦托管的Web服務(wù)器接收 發(fā)送來的HTTP請求，指定的資源可能包含邏輯輸入值（例如在一個文本框的值），以便以適當(dāng)?shù)母袷交貜?fù)HTTP響應(yīng)。 Web程序員可以利用任何技術(shù)（共同閘道介面，的ASP，ASP.NET，Java Servlets和等）來動態(tài)生成納入HTTP響應(yīng)的內(nèi)容。此時，客戶端的HTML瀏覽器從Web服務(wù)器發(fā)出的請求。</p><p>　　網(wǎng)絡(luò)的另一個顯

39、著的發(fā)展是從傳統(tǒng)的桌面程序變成HTTP的無國界有線協(xié)議。只要服務(wù)器發(fā)出響應(yīng)客戶,所有關(guān)于以前的交互作用被遺忘了。因此，作為Web開發(fā)人員，它是由你采取具體步驟，以“記住”信息（如在購物車中的物品）有關(guān)目前誰登錄到您的站點。你會在下一章看到，ASP.NET提供了許多方法來處理狀態(tài)，其中許多是很常見網(wǎng)絡(luò)平臺（會話變量，Cookie和應(yīng)用程序變量）以及一些新技術(shù)（視圖狀態(tài)，控制狀態(tài)，和緩存）。</p><p>　　了解

40、Web應(yīng)用程序和Web服務(wù)器</p><p>　　一個web應(yīng)用程序可以被理解為一個檔案集合（*.熱媒，*. asp和*.的ASPX，圖像文件等）和（如相關(guān)的組件。NET代碼庫）在一組特定的目錄中存儲給定的Web服務(wù)器。如第24章所示，Web應(yīng)用程序有一個特定的生命周期，并提供了許多活動（如初始啟動或最后關(guān)閉），可以連接到。</p><p>　　Web服務(wù)器是 接管網(wǎng)絡(luò)應(yīng)用的軟件產(chǎn)品，而且

41、通常提供集成安全等一系列相關(guān)服務(wù)的數(shù)量，文件傳輸協(xié)議（FTP）的支持，郵件交換服務(wù)，等等?；ヂ?lián)網(wǎng)信息服務(wù)（IIS）是微軟的企業(yè)級Web服務(wù)器的產(chǎn)品，它內(nèi)在的支持傳統(tǒng)的ASP以及ASP.NET Web應(yīng)用程序。</p><p>　　當(dāng)你建立ASP.NET Web應(yīng)用程序，你會經(jīng)常需要與IIS進行交互。請注意，IIS是不會自動選擇安裝Windows Server 2003或Windows XP專業(yè)版（無法安裝在Win

42、dows家用版IIS）的。因此，在你的開發(fā)機器配置不同時，您可能需要手動安裝本章所說的IIS程序。為此，只需訪問添加/從控制面板文件夾刪除程序小程序并選擇添加/刪除Windows組件。</p><p>　　工作與IIS虛擬目錄</p><p>　　在每一個虛擬目錄里單一的IIS有能力辦好許多Web應(yīng)用程序。每一個虛擬目錄映射到本地硬盤驅(qū)動器的物理目錄。因此，如果您創(chuàng)建一個新的虛擬目錄名為C

43、arsRUs，外界可以瀏覽到這個網(wǎng)站使用的網(wǎng)址，如http://www.CarsRUs.com（假設(shè)您的網(wǎng)站的IP地址已經(jīng)與整個世界的登記）。在內(nèi)部，該虛擬目錄映射到一個物理根目錄，如C：\ inetpub \ wwwroot的\ AspNetCarsSite，其中包含Web應(yīng)用程序的內(nèi)容。</p><p>　　當(dāng)您創(chuàng)建ASP.NET Web應(yīng)用程序使用Visual Studio 2005，您可以產(chǎn)生一個新的當(dāng)前

44、網(wǎng)站的虛擬目錄選項。不過，你也可以手動創(chuàng)建一個虛擬目錄。為了說明起見，假設(shè)你想創(chuàng)建一個簡單的Web應(yīng)用程序命名為汽車。第一步是創(chuàng)建一個你新文件夾以保存文件，構(gòu)成新的網(wǎng)站（例如，C：\ CodeTests \ CarsWebSite）集合。</p><p>　　下面，需要創(chuàng)建一個新的虛擬目錄舉辦汽車的網(wǎng)站。只需右鍵單擊默認(rèn)Web站點的IIS節(jié)點，然后從上下文菜單中選擇New?虛擬目錄。此菜單選擇啟動一個綜合向?qū)?。?/p>

45、過過去的歡迎屏幕，是你的網(wǎng)站的名稱（汽車）。接下來，您被要求指定您的硬盤驅(qū)動器包含各種文件和圖像的物理文件夾代表本網(wǎng)站（在此情況下，C：\ CodeTests \ CarsWebSite）。</p><p>　　在向?qū)У淖詈笠徊綍崾灸阈碌奶摂M目錄（如讀/寫訪問的文件它包含了一些基本特征你，能夠從一個網(wǎng)頁瀏覽器這些文件，能夠發(fā)射可執(zhí)行文件[例如，共同閘道介面應(yīng)用]等）。在這個例子中，只是默認(rèn)選擇（注意，您可以隨時

46、修改運行此工具后，使用不同的用鼠標(biāo)右鍵單擊屬性對話框在IIS集成箱您的選擇）。</p><p><b>　　原文2</b></p><p>　　The Role of the Global.asax File</p><p>　　At this point, an ASP.NET application may seem to be littl

47、e more than a set of *.aspx files and their respective web controls. While you could build a web application by simply linking a set of related web pages, you will most likely need a way to interact with the web applicat

48、ion as a whole. To this end, your ASP.NET web applications may choose to include an optional Global.asax file via the WebSite.</p><p>　　Add New Item menu option.</p><p>　　Simply put, Global.asax

49、 is just about as close to a traditional double-clickable *.exe that we can get in the world of ASP.NET, meaning this type represents the runtime behavior of the website itself. Once you insert a Global.asax file into a

50、web project, you will notice it is little more than a <script> block containing a set of event handlers:</p><p>　　<%@ Application Language="C#" %></p><p>　　<script runat

51、="server"></p><p>　　void Application_Start(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs on application startup</p><p&

52、gt;<b>　　}</b></p><p>　　void Application_End(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs on application shutdown</p><p

53、><b>　　}</b></p><p>　　void Application_Error(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs when an unhandled error occurs</p&

54、gt;<p><b>　　}</b></p><p>　　void Session_Start(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs when a new session is started&l

55、t;/p><p><b>　　}</b></p><p>　　void Session_End(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs when a session ends</p>

56、;<p><b>　　}</b></p><p><b>　　</script></b></p><p>　　Looks can be deceiving, however. At runtime, the code within this <script> block is assembled into a

57、 class type deriving from System.Web.HttpApplication. If you have a background in ASP.NET 1.x, you may recall that the Global.asax code-behind file literally did define a class deriving from HttpApplication.</p>&

58、lt;p>　　The Global Last Chance Exception Event Handler</p><p>　　First, let me point out the role of the Application_Error() event handler. Recall that a specific page may handle the Error event to process

59、any unhandled exception that occurred within the scope of the page itself. In a similar light, the Application_Error() event handler is the final place to handle an exception that was not handled by a specific page. As w

60、ith the page-level Error event, you are able to access the specific System.Exception using the inherited Server property:</p><p>　　void Application_Error(Object sender, EventArgs e)</p><p><b

61、>　　{</b></p><p>　　Exception ex = Server.GetLastError();</p><p>　　Response.Write(ex.Message);</p><p>　　Server.ClearError();</p><p><b>　　}</b></p&

62、gt;<p>　　Given that the Application_Error() event handler is the last chance exception handler for your web application, odds are that you would rather not report the error to the user, but you would like to log t

63、his information to the web server’s event log, for example:</p><p>　　<%@ Import Namespace = "System.Diagnostics"%></p><p><b>　　...</b></p><p>　　void Appl

64、ication_Error(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Log last error to event log.</p><p>　　Exception ex = Server.GetLastError();</p><p>　

65、　EventLog ev = new EventLog("Application");</p><p>　　ev.WriteEntry(ex.Message, EventLogEntryType.Error);</p><p>　　Server.ClearError();</p><p>　　Response.Write("This a

66、pp has bombed. Sorry!");</p><p><b>　　}</b></p><p>　　The HttpApplication Base Class </p><p>　　As mentioned, the Global.asax script is dynamically generated into a cl

67、ass deriving from the System.Web.HttpApplication base class, which supplies the same sort of functionality as the System.Web.UI.Page type.</p><p>　　Application This property allows you to interact with appli

68、cation-level variables, using the exposed HttpApplicationState type.</p><p>　　Request This property allows you to interact with the incoming HTTP request (via HttpRequest).</p><p>　　Respon

69、se This property allows you to interact with the incoming HTTP response (via HttpResponse).</p><p>　　Server This property gets the intrinsic server object for the current request (via HttpServerU

70、tility).</p><p>　　Session This property allows you to interact with session-level variables, using the exposed HttpSessionState type.</p><p><b>　　譯文2</b></p><p>　　

71、作者：P.S.Yu, H.Heiss, and D.M.Dias</p><p><b>　　國籍：德國</b></p><p>　　出處：ASP.NET 2.0 Web Pages and Web Controls</p><p>　　Global.asax文件的作用</p><p>　　ASP.NET應(yīng)用程序看起來是

72、一個*. aspx文件中各自的網(wǎng)絡(luò)控制設(shè)置。雖然可以通過建立起來的相關(guān)網(wǎng)頁設(shè)置一個Web應(yīng)用程序，你很可能需要一種整個互動的Web應(yīng)用程序。為此，ASP.NET Web應(yīng)用程序可以通過選擇一個可選的Global.asax網(wǎng)站?添加新項菜單選項文件。</p><p>　　簡單地說，Global.asax是一種類似于傳統(tǒng)的double-clickable *.exe文件，在ASP.NET世界，這意味著這種類型的網(wǎng)站代

73、表了本身運行時的行為。一旦你插入的一個Global.asax文件轉(zhuǎn)換成一個網(wǎng)頁專題研究,你會發(fā)現(xiàn)它是<腳本>包含一組事件處理器：</p><p>　　<%@ Application Language="C#" %></p><p>　　<script runat="server"></p><p

74、>　　void Application_Start(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs on application startup</p><p><b>　　}</b></p><

75、;p>　　void Application_End(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs on application shutdown</p><p><b>　　}</b></p>&l

76、t;p>　　void Application_Error(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs when an unhandled error occurs</p><p><b>　　}</b><

77、/p><p>　　void Session_Start(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs when a new session is started</p><p><b>　　}</b>

78、;</p><p>　　void Session_End(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　// Code that runs when a session ends</p><p><b>　　}</b></p

79、><p><b>　　</script></b></p><p>　　但是，在運行時，在此的<SCRIPT>塊生成一個類派生類型的System.Web.HttpApplication組裝代碼。如果在ASP.NET 1.x的背景下，你可能會記得，Global.asax代碼隱藏文件字面上沒有定義一個類HttpApplication的義務(wù)。</p&

80、gt;<p>　　Global最后機會異常事件處理</p><p>　　首先，請允許我指出， Application_Error（）事件處理程序的作用點。回想一下，一個特定的頁面能處理網(wǎng)頁本身范圍內(nèi)發(fā)生的錯誤事件。在類似的情況，Application_Error（）處理器是最后的地方，不是處理異常事件的一個特定頁面。如同頁面級錯誤事件，您可以訪問特定的System.Exception以繼承服務(wù)器的屬

81、性：</p><p>　　void Application_Error(Object sender, EventArgs e)</p><p><b>　　{</b></p><p>　　Exception ex = Server.GetLastError();</p><p>　　Response.Write(ex.M

82、essage);</p><p>　　Server.ClearError();</p><p><b>　　}</b></p><p>　　鑒于Application_Error（）事件處理程序是您的Web應(yīng)用程序異常處理程序的最后機會，你不報告錯誤給使用者，你會記錄這些信息的Web服務(wù)器事件日志，例如：</p><p>

83、;　　<%@ Import Namespace = "System.Diagnostics"%></p><p><b>　　...</b></p><p>　　void Application_Error(Object sender, EventArgs e)</p><p><b>　　{</

84、b></p><p>　　// Log last error to event log.</p><p>　　Exception ex = Server.GetLastError();</p><p>　　EventLog ev = new EventLog("Application");</p><p>　　ev.

85、WriteEntry(ex.Message, EventLogEntryType.Error);</p><p>　　Server.ClearError();</p><p>　　Response.Write("This app has bombed. Sorry!");</p><p><b>　　}</b></p&

86、gt;<p>　　HttpApplication基類</p><p>　　如上所述，Global.asax腳本動態(tài)生成到一個從System.Web.HttpApplication基類，它提供作為System.Web.UI.Page同一種類型的派生類。</p><p>　　應(yīng)用程序:此屬性允許您交互應(yīng)用程序級的變量，使用公開的HttpApplicationState類型。<

87、;/p><p>　　請求:要求此屬性允許您進行互動交流傳入的HTTP請求（通過的HttpRequest）。</p><p>　　回應(yīng):此屬性允許您進行互動交流傳入的HTTP響應(yīng)（通過中HttpResponse）。</p><p>　　服務(wù)器:此屬性獲取當(dāng)前請求（通過HttpServerUtility）的內(nèi)在服務(wù)器對象。</p><p>　　會話: