基于.NET的航空訂票系統(tǒng)設(shè)計(jì)與開(kāi)發(fā),基于,NET,航空,訂票,系統(tǒng),設(shè)計(jì),開(kāi)發(fā) 編號(hào) 無(wú)錫太湖學(xué)院 畢業(yè)設(shè)計(jì)（論文） 相關(guān)資料 題目： 基于.NET的航空訂票系統(tǒng) 設(shè)計(jì)與開(kāi)發(fā) 信機(jī) 系 計(jì)算機(jī)科學(xué)與技術(shù) 專業(yè) 學(xué) 號(hào)： 　　　 0921131　　 　　 學(xué)生姓名： 包培培 指導(dǎo)教師：　李朝鋒 （職稱：副教授 ） （職稱： ） 2013年5月25日 目 錄 一、畢業(yè)設(shè)計(jì)（論文）開(kāi)題報(bào)告 二、畢業(yè)設(shè)計(jì)（論文）外文資料翻譯及原文 三、學(xué)生“畢業(yè)論文（論文）計(jì)劃、進(jìn)度、檢查及落實(shí)表” 四、實(shí)習(xí)鑒定表 無(wú)錫太湖學(xué)院 畢業(yè)設(shè)計(jì)（論文） 開(kāi)題報(bào)告 題目： 基于.NET的航空訂票系統(tǒng) 設(shè)計(jì)與開(kāi)發(fā) 信機(jī) 系 計(jì)算機(jī)科學(xué)與技術(shù) 專業(yè) 學(xué) 號(hào)： 0921131 學(xué)生姓名： 包培培 指導(dǎo)教師： 李朝鋒 （職稱：副教授 ） （職稱： ） 2012年11月20日 課題來(lái)源 導(dǎo)師指定 科學(xué)依據(jù)（包括課題的科學(xué)意義；國(guó)內(nèi)外研究概況、水平和發(fā)展趨勢(shì)；應(yīng)用前景等） 在社會(huì)信息化日益發(fā)展的今天，航空客運(yùn)作為現(xiàn)代交通中最快捷最方便的一種，給人們的生活、出行帶來(lái)了極大的方便。但，它的管理和規(guī)范問(wèn)題是一個(gè)難點(diǎn)，訂票是客運(yùn)業(yè)務(wù)中最基本的業(yè)務(wù)，涉及管理與客戶服務(wù)等方面。隨著航空客運(yùn)業(yè)務(wù)的多年發(fā)展，過(guò)去傳統(tǒng)的訂票方式已不能滿足現(xiàn)代客運(yùn)業(yè)務(wù)劇增的客觀要求了，這使得一種全新的售票方式誕生了，即網(wǎng)絡(luò)訂票方式。這種訂票方式可以解決手工操作訂票高峰時(shí)帶來(lái)的大量數(shù)據(jù)處理問(wèn)題，使得機(jī)票訂購(gòu)與日常管理得到了改善，并為客戶提供方便快捷的訂票服務(wù)。 近年來(lái)，計(jì)算機(jī)與互聯(lián)網(wǎng)技術(shù)的日益成熟促進(jìn)了航空網(wǎng)上訂票系統(tǒng)的發(fā)展。網(wǎng)上訂票的優(yōu)越性使得國(guó)內(nèi)外越來(lái)越多的航空公司著手研制自己的網(wǎng)上訂票系統(tǒng)，因?yàn)樗哂芯薮蟮默F(xiàn)代商業(yè)價(jià)值。它打破了常規(guī)的買賣方式，使得航空公司可以很好的面對(duì)整個(gè)世界，為客戶提供了全天候的服務(wù)。 一個(gè)完善的航空訂票系統(tǒng)是由航空管理和計(jì)算機(jī)網(wǎng)絡(luò)服務(wù)相結(jié)合的產(chǎn)物。通過(guò)計(jì)算機(jī)網(wǎng)絡(luò)管理使得航空公司對(duì)大量的數(shù)據(jù)及信息能及時(shí)準(zhǔn)確的進(jìn)行分析，同時(shí)滿足了當(dāng)代客戶的需求。也使得航空訂票事業(yè)得到了發(fā)展，更上了時(shí)代的腳步。 研究?jī)?nèi)容 本系統(tǒng)是能夠完成客戶登錄、注冊(cè)，查詢航班班次，訂購(gòu)機(jī)票，退票等功能；航空管理能夠完成增刪改航班等功能。 ① 客戶的登錄：新客戶可以注冊(cè)之后登錄，帶有忘記密碼的功能； ② 航班的查詢：可以查詢某個(gè)航班的情況； ③訂購(gòu)機(jī)票：通過(guò)查詢系統(tǒng)，客戶可以根據(jù)自己的情況找到航班，然后進(jìn)行訂票； ④退票：通過(guò)查詢系統(tǒng)，客戶可以根據(jù)自己的名字找到訂票信息，進(jìn)行退票。 ⑤管理員對(duì)用戶信息、航班信息、訂單信息、管理員自身信息、公告信息、旅游資訊、留言信息進(jìn)行增刪改及查詢。 數(shù)據(jù)庫(kù)的需求： 因?yàn)闊o(wú)法連接到大型數(shù)據(jù)庫(kù)，只能在本機(jī)上安裝SQL Server 2000數(shù)據(jù)庫(kù)軟件。在此數(shù)據(jù)庫(kù)中建立需要的表來(lái)保存數(shù)據(jù)。 擬采取的研究方法、技術(shù)路線、實(shí)驗(yàn)方案及可行性分析 在軟件的定義時(shí)期，完成軟件開(kāi)發(fā)工程的總目標(biāo)，導(dǎo)出實(shí)現(xiàn)系統(tǒng)目標(biāo)應(yīng)該采用的策略及軟件必須完成的功能，估計(jì)完成該系統(tǒng)所需資源及成本，制定進(jìn)度計(jì)劃。在軟件開(kāi)發(fā)時(shí)期，具體設(shè)計(jì)和實(shí)現(xiàn)在定義時(shí)期的軟件功能。 本系統(tǒng)是利用ASP.NET來(lái)實(shí)現(xiàn)的，并采用SQL Server 2000數(shù)據(jù)庫(kù)來(lái)存放數(shù)據(jù)信息，開(kāi)發(fā)一個(gè)滿足以前功能的訂票系統(tǒng)。 在了解軟件及收集本系統(tǒng)所需的信息后，開(kāi)始逐個(gè)模塊的對(duì)軟件進(jìn)行設(shè)計(jì)實(shí)現(xiàn)，完成一些基本功能后開(kāi)始對(duì)界面進(jìn)行美化，再完善一些功能。最后，對(duì)完成的軟件進(jìn)行測(cè)試調(diào)試。 從經(jīng)濟(jì)可行性來(lái)說(shuō)，與傳統(tǒng)方式相比，本系統(tǒng)是高效率、低成本、高質(zhì)量的系統(tǒng)；從技術(shù)可行性來(lái)說(shuō)，系統(tǒng)實(shí)現(xiàn)依靠相對(duì)熟悉的.NET語(yǔ)言和SQL Server 2000數(shù)據(jù)庫(kù)系統(tǒng)，其基本操作是對(duì)數(shù)據(jù)庫(kù)的增刪改及查詢等操作，暫不存在技術(shù)問(wèn)題；從操作可行性來(lái)說(shuō)，系統(tǒng)簡(jiǎn)單明了，界面簡(jiǎn)潔友好，操作方便，客戶不需掌握數(shù)據(jù)庫(kù)等相關(guān)知識(shí)。 研究計(jì)劃及預(yù)期成果 研究計(jì)劃： 1、2012年11月12日到2012年12月16日，完成任務(wù)書(shū)及開(kāi)題報(bào)告； 2、2012年12月到2013年01月，外文翻譯資料，系統(tǒng)設(shè)計(jì)； 3、2013年03月，完成軟件，開(kāi)始撰寫論文； 4、2013年04月，完成軟件測(cè)試、驗(yàn)收； 5、2013年05月25日，上交論文、軟件，根據(jù)導(dǎo)師意見(jiàn)修改及完善論文； 6、2013年06月1日，進(jìn)行畢業(yè)答辯。 預(yù)期成果：能按計(jì)劃完成畢業(yè)設(shè)計(jì)和論文，在研究?jī)?nèi)容中所涉及的功能都能實(shí)現(xiàn)。 特色或創(chuàng)新之處 本課題是基于.NET架構(gòu)下的ASP.NET和SQL Server 2000技術(shù)聯(lián)合開(kāi)發(fā)完成。 1、 對(duì)訂票系統(tǒng)的各種基本功能有考慮，將信息進(jìn)行分類管理； 2、 設(shè)計(jì)界面簡(jiǎn)單、明了，便于管理人員和客戶進(jìn)行操作； 能保證整個(gè)系統(tǒng)架構(gòu)的穩(wěn)定性和安全性； 已具備的條件和尚需解決的問(wèn)題 已具備的條件： 1、 硬件方面：有一臺(tái)計(jì)算機(jī)； 2、 軟件方面：已裝有Microsoft Visual Studio 2005 及SQL Server 2000； 已了解整個(gè)系統(tǒng)該完成的功能。 指導(dǎo)教師意見(jiàn) 指導(dǎo)教師簽名： 年 月 日 教研室（學(xué)科組、研究所）意見(jiàn) 教研室主任簽名： 年 月 日 系意見(jiàn) 主管領(lǐng)導(dǎo)簽名： 年 月 日 英文原文 ASP.NET Technique 1.Building ASP.NET Pages ASP.NET and the .NET Framework ASP.NET is part of Microsoft's overall .NET framework, which contains a vast set of programming classes designed to satisfy any conceivable programming need. In the following two sections, you learn how ASP.NET fits within the .NET framework, and you learn about the languages you can use in your ASP.NET pages. The .NET Framework Class Library agine that you are Microsoft. Imagine that you have to support multiple programming languages—such as Visual Basic, JScript, and C++. A great deal of the functionality of these programming languages overlaps. For example, for each language, you would have to include methods for accessing the file system, working with databases, and manipulating strings. Furthermore, these languages contain similar programming constructs. Every language, for example, can represent loops and conditionals. Even though the syntax of a conditional written in Visual Basic differs from the syntax of a conditional written in C++, the programming function is the same. Finally, most programming languages have similar variable data types. In most languages, you have some means of representing strings and integers, for example. The maximum and minimum size of an integer might depend on the language, but the basic data type is the same. Maintaining all this functionality for multiple languages requires a lot of work. Why keep reinventing the wheel? Wouldn't it be easier to create all this functionality once and use it for every language? The .NET Framework Class Library does exactly that. It consists of a vast set of classes designed to satisfy any conceivable programming need. For example, the .NET framework contains classes for handling database access, working with the file system, manipulating text, and generating graphics. In addition, it contains more specialized classes for performing tasks such as working with regular expressions and handling network protocols. The .NET framework, furthermore, contains classes that represent all the basic variable data types such as strings, integers, bytes, characters, and arrays. Most importantly, for purposes of this book, the .NET Framework Class Library contains classes for building ASP.NET pages. You need to understand, however, that you can access any of the .NET framework classes when you are building your ASP.NET pages. Understanding Namespaces As you might guess, the .NET framework is huge. It contains thousands of classes (over 3,400). Fortunately, the classes are not simply jumbled together. The classes of the .NET framework are organized into a hierarchy of namespaces. ASP Classic Note In previous versions of Active Server Pages, you had access to only five standard classes (the Response, Request, Session, Application, and Server objects). ASP.NET, in contrast, provides you with access to over 3,400 classes! A namespace is a logical grouping of classes. For example, all the classes that relate to working with the file system are gathered together into the System.IO namespace. The namespaces are organized into a hierarchy (a logical tree). At the root of the tree is the System namespace. This namespace contains all the classes for the base data types, such as strings and arrays. It also contains classes for working with random numbers and dates and times. You can uniquely identify any class in the .NET framework by using the full namespace of the class. For example, to uniquely refer to the class that represents a file system file (the File class), you would use the following: System.IO.File System.IO refers to the namespace, and File refers to the particular class. NOTE You can view all the namespaces of the standard classes in the .NET Framework Class Library by viewing the Reference Documentation for the .NET Framework. Standard ASP.NET Namespaces The classes contained in a select number of namespaces are available in your ASP.NET pages by default. (You must explicitly import other namespaces.) These default namespaces contain classes that you use most often in your ASP.NET applications: System— Contains all the base data types and other useful classes such as those related to generating random numbers and working with dates and times. System.Collections— Contains classes for working with standard collection types such as hash tables, and array lists. System.Collections.Specialized— Contains classes that represent specialized collections such as linked lists and string collections. System.Configuration— Contains classes for working with configuration files (Web.config files). System.Text— Contains classes for encoding, decoding, and manipulating the contents of strings. System.Text.RegularExpressions— Contains classes for performing regular expression match and replace operations. System.Web— Contains the basic classes for working with the World Wide Web, including classes for representing browser requests and server responses. System.Web.Caching— Contains classes used for caching the content of pages and classes for performing custom caching operations. System.Web.Security— Contains classes for implementing authentication and authorization such as Forms and Passport authentication. System.Web.SessionState— Contains classes for implementing session state. System.Web.UI— Contains the basic classes used in building the user interface of ASP.NET pages. System.Web.UI.HTMLControls— Contains the classes for the HTML controls. System.Web.UI.WebControls— Contains the classes for the Web controls. .NET Framework -Compatible Languages For purposes of this book, you will write the application logic for your ASP.NET pages using Visual Basic as your programming language. It is the default language for ASP.NET pages. Although you stick to Visual Basic in this book, you also need to understand that you can create ASP.NET pages by using any language that supports the .NET Common Language Runtime. Out of the box, this includes C#, JScript.NET, and the Managed Extensions to C++. NOTE Dozens of other languages created by companies other than Microsoft have been developed to work with the .NET framework. Some examples of these other languages include Python, SmallTalk, Eiffel, and COBOL. This means that you could, if you really wanted to, write ASP.NET pages using COBOL. Regardless of the language that you use to develop your ASP.NET pages, you need to understand that ASP.NET pages are compiled before they are executed. This means that ASP.NET pages can execute very quickly. The first time you request an ASP.NET page, the page is compiled into a .NET class, and the resulting class file is saved beneath a special directory on your server named Temporary ASP.NET Files. For each and every ASP.NET page, a corresponding class file appears in the Temporary ASP.NET Files directory. Whenever you request the same ASP.NET page in the future, the corresponding class file is executed. When an ASP.NET page is compiled, it is not compiled directly into machine code. Instead, it is compiled into an intermediate-level language called Microsoft Intermediate Language (MSIL). All .NET-compatible languages are compiled into this intermediate language. An ASP.NET page isn't compiled into native machine code until it is actually requested by a browser. At that point, the class file contained in the Temporary ASP.NET Files directory is compiled with the .NET framework Just in Time (JIT) compiler and executed. The magical aspect of this whole process is that it happens automatically in the background. All you have to do is create a text file with the source code for your ASP.NET page, and the .NET framework handles all the hard work of converting it into compiled code for you. ASP CLASSIC NOTE What about VBScript? Before ASP.NET, VBScript was the most popular language for developing Active Server Pages. ASP.NET does not support VBScript, and this is good news. Visual Basic is a superset of VBScript, which means that Visual Basic has all the functionality of VBScript and more. So, you have a richer set of functions and statements with Visual Basic. Furthermore, unlike VBScript, Visual Basic is a compiled language. This means that if you use Visual Basic to rewrite the same code that you wrote with VBScript, you can get better performance. If you have worked only with VBScript and not Visual Basic in the past, don't worry. Since VBScript is so closely related to Visual Basic, you'll find it easy to make the transition between the two languages. NOTE Microsoft includes an interesting tool named the IL Disassembler (ILDASM) with the .NET framework. You can use this tool to view the disassembled code for any of the ASP.NET classes in the Temporary ASP.NET Files directory. It lists all the methods and properties of the class and enables you to view the intermediate-level code. This tool also works with all the ASP.NET controls discussed in this chapter. For example, you can use the IL Disassembler to view the intermediate-level code for the TextBox control (located in a file named System.Web.dll). Introducing ASP.NET Controls ASP.NET controls provide the dynamic and interactive portions of the user interface for your Web application. The controls render the content that the users of your Web site actually see and interact with. For example, you can use controls to create HTML form elements, interactive calendars, and rotating banner advertisements. ASP.NET controls coexist peacefully with HTML content. Typically, you create the static areas of your Web pages with normal HTML content and create the dynamic or interactive portions with ASP.NET controls. The best way to understand how ASP.NET controls work in an HTML page is to look at a simple Web Forms Page. Adding Application Logic to an ASP.NET Page The second building block of an ASP.NET page is the application logic, which is the actual programming code in the page. You add application logic to a page to handle both control and page events. If a user clicks a Button control within an HTML form, for example, the Button control raises an event (the Click event). Typically, you want to add code to the page that does something in response to this event. For example, when someone clicks the Button control, you might want to save the form data to a file or database. Controls are not the only things that can raise events. An ASP.NET page itself raises several events every time it is requested. For example, whenever you request a page, the page's Load event is triggered. You can add application logic to the page that executes whenever the Load event occurs. 2.Building Forms with Web Server Controls Building Smart Forms You use several of the basic Web controls to represent standard HTML form elements such as radio buttons, text boxes, and list boxes. You can use these controls in your ASP.NET pages to create the user interface for your Web application. The following sections provide detailed overviews and programming samples for each of these Web controls. Controlling Page Navigation In the following sections, you learn how to control how a user moves from one ASP.NET page to another. First, you learn how to submit an HTML form to another page and retrieve form information. Next, you learn how to use the Redirect() method to automatically transfer a user to a new page. Finally, you learn how to link pages together with the HyperLink control. Applying Formatting to Controls In the following sections, you learn how to make more attractive Web forms. First, you look at an overview of the formatting properties common to all Web controls; they are the formatting properties of the base control class. Next, you learn how to apply Cascading Style Sheet styles and classes to Web controls. 3.Performing Form Validation with Validation Controls Using Client-side Validation Traditionally, Web developers have faced a tough choice when adding form validation logic to their pages. You can add form validation routines to your server-side code, or you can add the validation routines to your client-side code. The advantage of writing validation logic in client-side code is that you can provide instant feedback to your users. For example, if a user neglects to enter a value in a required form field, you can instantly display an error message without requiring a roundtrip back to the server. People really like client-side validation. It looks great and creates a better overall user experience. The problem, however, is that it does not work with all browsers. Not all browsers support JavaScript, and different versions of browsers support different versions of JavaScript, so client-side validation is never guaranteed to work. For this reason, in the past, many developers decided to add all their form validation logic exclusively to server-side code. Because server-side code functions correctly with any browser, this course of action was safer. Fortunately, the Validation controls discussed in this chapter do not force you to make this difficult choice. The Validation controls automatically generate both client-side and server-side code. If a browser is capable of supporting JavaScript, client-side validation scripts are automatically sent to the browser. If a browser is incapable of supporting JavaScript, the validation routines are automatically implemented in server-side code. You should be warned, however, that client-side validation works only with Microsoft Internet Explorer version 4.0 and higher. In particular, the client-side scripts discussed in this chapter do not work with any version of Netscape Navigator. Requiring Fields:The RequiredFieldValidator Control You use RequiredFieldValidator in a Web form to check whether a control has a value. Typically, you use this control with a TextBox control. However, nothing is wrong with using RequiredFieldValidator with other input controls such as RadioButtonList. Validating Expression:The RegularExpressionValidator Control You can use RegularExpressionValidator to match the value entered into a form field to a regular expression. You can use this control to check whether a user has entered, for example, a valid e-mail address, telephone number, or username or password. Samples of how to use a regular expression to perform all these validation tasks are provided in the following sections. Comparing Values:The CompareValidator Control The CompareValidator control performs comparisons between the data entered into a form field and another value. The other value can be a fixed value, such as a particular number, or a value entered into another control. Summarizing Errors:The ValidationSummary Control Imagine that you have a form with 50 form fields. If you use only the Validation controls discussed in the previous sections of this chapter to display errors, seeing an error message on the page might be difficult. For example, you might have to scroll down to the 48th form field to find the error message. Fortunately, Microsoft includes a ValidationSummary control with the Validation controls. You can use this control to summarize all the errors at the top of a page, or wherever else you want. McDonald, Zipuzita the Advanced ASP.NET 3.5 Programming (2nd Edition) 中文譯文 ASP.NET技術(shù) 1.構(gòu)建ASP.NET頁(yè)面 ASP 和ASP.NET結(jié)構(gòu) ASP.NET 是微軟.NET framework整體的一部分，它包含一組大量的編程用的類，滿足各種編程需要。在下列的二個(gè)部分中，你如何學(xué)會(huì) ASP.NET 很適合的放在.NET framework，和學(xué)會(huì)能在你的 ASP.NET 頁(yè)面中使用語(yǔ)言。 .NET類庫(kù) 假想你是微軟。假想你必須支持大量的編程語(yǔ)言-比如 Visual Basic 、 C# 和 C++. 這些編程語(yǔ)言的很多功能具有重疊性。舉例來(lái)說(shuō)，對(duì)于每一種語(yǔ)言，你必須包括存取文件系統(tǒng)、與數(shù)據(jù)庫(kù)協(xié)同工作和操作字符串的方法。 此外，這些語(yǔ)言包含相似的編程構(gòu)造。每種語(yǔ)言，舉例來(lái)說(shuō)，都能夠使用循環(huán)語(yǔ)句和條件語(yǔ)句。即使用 Visual Basic 寫的條件語(yǔ)句的語(yǔ)法不與 用C++ 寫的不一樣，程序的功能也是相同的。 最后，大多數(shù)的編程語(yǔ)言有相似的數(shù)據(jù)變量類型。以大多數(shù)的語(yǔ)言，你有設(shè)定字符串類型和整型數(shù)據(jù)類型的方法。舉例來(lái)說(shuō)，整型數(shù)據(jù)最大值和最小值可能依賴語(yǔ)言的種類，但是基本的數(shù)據(jù)類型是相同的。 對(duì)于多種語(yǔ)言來(lái)說(shuō)維持這一功能需要很大的工作量。為什么繼續(xù)再創(chuàng)輪子? 對(duì)所有的語(yǔ)言創(chuàng)建這種功能一次，然后把這個(gè)功能用在每一種語(yǔ)言中豈不是更容易。 .NET類庫(kù)不完全是那樣。它含有大量的滿足編程需要的類。舉例來(lái)說(shuō)，.NET類庫(kù)包含處理數(shù)據(jù)庫(kù)訪問(wèn)的類和文件協(xié)同工作，操作文本和生成圖像。除此之外，它包含更多特殊的類用在正則表達(dá)式和處理Web協(xié)議。 .NET framework，此外包含支持所有的基本變量數(shù)據(jù)類型的類，比如：字符串、整型、字節(jié)型、字符型和數(shù)組。 最重要地，寫這一本書(shū)的目的，.NET類庫(kù)包含構(gòu)建的 ASP.NET 頁(yè)面的類。然而你需要了解當(dāng)你構(gòu)建.NET頁(yè)面的時(shí)候能夠訪問(wèn).NET framework 的任意類。 理解命名空間 正如你猜測(cè)的，.NET framework是龐大的。它包含數(shù)以千計(jì)的類(超過(guò) 3，400) 。幸運(yùn)地，類不是簡(jiǎn)單的堆在一起。.NET framework的類被組織成有層次結(jié)構(gòu)的命名空間。 ASP Classic Note 在先前的ASP中，你僅僅能夠訪問(wèn)五個(gè)標(biāo)準(zhǔn)類。相比之下 ASP.NET 提供超過(guò) 3，400個(gè)類! 一個(gè)命名空間包含一組邏輯的類。舉例來(lái)說(shuō)，涉及到與文件系統(tǒng)協(xié)同工作的類就集合在System.IO 命名空間中。 命名空間被組織成一個(gè)層次結(jié)構(gòu)(一棵邏輯樹(shù)) 。樹(shù)根就是SYSTEM 命名空間。這個(gè)命名空間包含基本的數(shù)據(jù)類型的所有的類，例如：字符串、數(shù)組，還包含提供隨機(jī)數(shù)字和日期的類。 你通過(guò)完整的類的命名空間能唯一識(shí)別任何的類在.NET framework中的位置。舉例來(lái)說(shuō)，指定找到一個(gè)the File class 類，按如下操: System.IO.文件 System.IO指命名空間 ，而文件指定特定的類。 提示 你能夠?yàn)g覽.NET Framework所有的標(biāo)準(zhǔn)類的命名空間。通過(guò).NET Framework 的參考文檔可以瀏覽類庫(kù)。 標(biāo)準(zhǔn)的ASP.NET命名空間 在默認(rèn)情況下，在你的ASP.NET頁(yè)面中，類被包含在一個(gè)選定的命名空間中這些默認(rèn)的命名空間使你在ASP.NET中最常用到的。 System 命名空間- 包含所有的基本數(shù)據(jù)類型和其他有用的類，例如：那些關(guān)于產(chǎn)生隨機(jī)數(shù)字和日期的類。 System.Collections命名空間- 包含的類是標(biāo)準(zhǔn)的集合類，例如：哈希表，數(shù)組列表。 System.Collections.Specialized 命名空間- 包含特殊的集合類，例如：連接列表和字符串集合。 System.Configuration 命名空間- 包括Web.config files類。 System.Text命名空間-包含編碼，解碼和操作字符串內(nèi)容的類。 System.Text.RegularExpressions命名空間- 包含的是匹配正則表達(dá)式和替代操作類。 System.Web 命名空間-工作在