人人文库网 > 图纸下载 > 毕业设计 > 基于ASP.NET的毕业设计（论文）管理系统【带程序】

外文翻译--ASP.NET和.NET框架.doc

基于ASP.NET的毕业设计（论文）管理系统【带程序】

资源目录

基于ASP.NET的毕业设计（论文）管理系统【带程序】.rar

计划周记进度检查表.xls---(点击预览)

相关资料.doc

计划周记进度检查表.xls

论文管理系统.rar

　　　　摘要

基于Web的毕业设计管理系统是在网络环境的支持下，开展学生选题和信息查询的一种先进模式，发挥学生选择课题的自主性，提高学校课题管理效率。网络选题具有其它技术手段无可比拟的优越性，因此世界各国尤其是发达国家无不对此给予高度的重视。本程序运用ASP.NET语言和SQL Server 2005数据库进行开发，因此开发的难度大大地降低了。

　　　毕业设计管理是高校必不可缺的组成部分，一直以来，学院教学管理工作人员使用传统人工的方式进行论文选题的管理，模式多种多样，如：学院指定教师与所带毕业设计的学生的对应关系，由教师和学生联系后确定题目；又如：学院汇总选题后，由各班学生分别进行选题和汇总，学院最终进行毕业选题的分配，这种管理方式存在着许多缺点，如：效率低、容易出错，实时性和互动性不强等，在发挥学生特长、更有效地通过毕业设计强化学生知识体系的目标不吻合，也无法实现学分制下教学管理的要求。

关键词：毕业设计；管理系统；ASP.NET；SQL Server 2005

摘要III

AbstractIV

目录IV

1 绪论1

　　1.1 本课题的研究背景和意义1

　　1.2 国内外的发展概况1

　　1.3 本课题应达到的要求1

2 系统开发环境介绍3

　　2.1 ASP.NET简介3

　　2.2 ADO.NET技术介绍4

　　2.3 JavaScript 介绍4

　　2.4 HTML语言4

　　2.5 SQL Server 2005数据库简介5

3 需求分析7

　　3.1 开发环境及其需求7

　　　3.1.1 硬件条件7

　　　3.1.2 系统平台7

　　　3.1.3运行需求7

　　　3.1.4 系统功能需求7

　　3.2 系统架构7

4 总体设计9

　　4.1 系统功能模块9

　　4.2 数据库设计10

　　　4.2.1 E-R图10

　　　4.2.2 表设计13

5 详细设计17

　　5.1 用户登录实现17

　　5.2 管理员功能实现18

　　　5.2.1 系统管理18

　　　5.2.2 用户管理20

　　　5.2.3 选题管理25

　　　5.2.4 课题管理27

　　　5.2.5 新闻公告管理28

　　　5.2.6 成绩信息管理29

　　5.3 指导老师功能实现30

　　　5.3.1 指导老师信息管理31

　　　5.3.2 课题管理32

　　　5.3.3 成绩管理35

　　　5.3.4 选题情况36

　　　5.3.5 系统公告38

　　5.4 学生功能实现39

　　　5.4.1 账号管理39

　　　5.4.2 课题管理42

　　　5.4.3 系统公告44

6 结论与展望47

致谢49

参考文献50

1 绪论

1.1 本课题的研究背景和意义

　　　本课题来源于无锡太湖学院信机系对毕业生毕业设计进程管理的实际需要，目标是提高系部对毕业生毕业设计全程监控、对毕业设计前期、中期、后期工作情况进行检查等相关工作的效率，并围绕此管理目标对系统所需要的各毕业生基本信息、课题基本信息、学生毕业设计完成情况基本信息、指导教师指导情况基本信息、系统后台数据库等进行管理和维护。系统开发的总体任务是实现毕业设计整个进程管理工作的流程化、系统化和规范化[1]。

　　　本课题涉及的知识有：面向对象程序设计，计算机网络基础，Web程序设计（熟悉ASP.NET），网页制作基础（熟悉网页制作工具软件），数据库原理，Visual Studio.NET集成开发环境，SQL Server 2005数据库，信息管理系统等。

　　　本课题学生将在老师的指导下，学习基于Web的毕业设计管理系统的前台界面设计、后台数据库概念和逻辑设计以及后台数据库的具体实现，同时对Web管理系统设计的合理性、实用性、安全性进行深入的研究，并设计实现基于Web的毕业设计管理系统的设计与实现（进程管理模块），并能投入实际使用。通过毕业设计培养学生良好的学习研究、综合设计、编程能力和工程实践能力，为学生日后的继续学习、研究和从事计算机网络、Web数据库应用开发方面相关工作奠定良好的基础[2]。

1.2 国内外的发展概况

　　　目前，运用先进的管理信息系统及软件开发平台，对信息进行科学化和网络化管理，己经成为国内外高校信息系统的发展趋势。其中，毕业设计信息网络管理系统使毕业生在毕业设计的整个过程中以及教师对毕业设计信息管理的过程中实现了系统化，规范化，无纸化。

　　　本系统是针对院系级毕业设计教务管理工作，研究、设计并开发的基于Web的毕业设计管理系统，采用ASP.NET和SQL Server 2005作为开发工具[3]。在开发过程中首先分析了其主要的业务流程和信息交流交互的内容，然后又结合了学校对毕业设计环节的管理标准和要求，经过系统的功能设计和数据库设计等过程，最终实现了系统要求的全部功能。

　　　本论文从系统需求分析、总体设计、详细设计、系统实现和系统测试这五个角度对系统的开发过程进行了详细的介绍，并对该系统的主要特点以及采用的主要系统开发工具进行了简单的介绍。

1.3 本课题应达到的要求

　　　通过结合ASP.NET和SQL Server 2005开发工具开发一个毕业设计管理系统，系统应该包含的基本功能包括网站公告，学生信息管理，教师信息管理，论文信息管理，论文审核，论文成绩管理等功能模块。

基于ASP.NET的毕业设计（论文）管理系统.jpg

内容简介：: ASP.NET and the .NET FrameworkASP.NET is part of Microsofts 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 LibraryImagine that you are Microsoft. Imagine that you have to support multiple programming languagessuch 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? Wouldnt 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 NamespacesAs 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 NoteIn 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.FileSystem.IO refers to the namespace, and File refers to the particular class.NOTEYou 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 NamespacesThe 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 LanguagesFor 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 (and the most popular programming language in the world). 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# (pronounced See Sharp), JScript.NET (the .NET version of JavaScript), and the Managed Extensions to C+.NOTEThe CD included with this book contains C# versions of all the code samples.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 isnt 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 NOTEWhat 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, dont worry. Since VBScript is so closely related to Visual Basic, youll find it easy to make the transition between the two languages.NOTEMicrosoft 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 ControlsASP.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.A Simple ASP.NET PageLets start by looking at a normal, everyday HTML page. Youll convert this page into an ASP.NET page in a moment. First, open either Web Matrix or Notepad on your computer and enter the HTML page contained in Listing 1.1. After you finish entering the HTML page, save it with the name SimpleHTML.aspx in your inetpub/wwwroot directory.NOTEWhen you create ASP.NET pages, be sure to save them in a directory that your Web server can access. You need to save your pages in the inetpub/wwwroot directory, a subdirectory of the inetpub/wwwroot directory, or within a virtual directory of your Web server.After you save a page, do not open the page directly in your Web browser by typing the file path of the page. If your Web server is located on the same computer as your Web browser, open the page by entering the pages address in the Address Bar of your browser. For example, if the page is named simpleHTML.aspx, open the page by typing the following text into your browsers Address Bar:http:/localhost/simpleHTML.aspxFor purposes of this book, Ill assume that you are using either Web Matrix or Notepad to create your Web pages. Web Matrix is included on the CD that accompanies this book. However, there is nothing wrong with using other text editors or Web development environments such as Microsoft Visual Studio .NET, Microsoft Visual Interdev, Allaires Homesite, or TextPad. Any program that can save a file as plain text will work fine.TIPWhen youre saving a file with Notepad, remember to pick All Types as the value in the Save As Type box in the Save As dialog box. If you dont choose this option, Notepad automatically adds the extension .txt to the name of your file. An alternative method of preventing .txt from being appended to your filename is to place the filename in quotation marks when saving the file.Listing 1.1 SimpleHTML.aspxSimple HTML PageUsername:Comments:The C# version of this code can be found on the CD-ROM.The page in Listing 1.1 contains a simple HTML form that includes a text field for a username and a text area for comments. This form might be used, for example, in a simple guest book application at a Web site. You might notice that the HTML form posts back to itself (the ACTION attribute of the tag submits the form data to SimpleHTML.aspx). So, when the Add Comment button is clicked, the same form appears once again.The HTML form in Listing 1.1 doesnt contain any ASP.NET controls. Now open the page in a Web browser (Microsoft Internet Explorer or Netscape Navigator); then try entering a username and some comments and submitting the form. Notice that the data you enter into the form fields disappears every time you submit the form.Now modify the page in Listing 1.1 so that it uses ASP.NET controls rather than the standard HTML form elements. Youre going to convert the form fields into smart server-side form fields. Enter the page contained in Listing 1.2 and save the file with the name SimpleASPX.aspx in a directory that your Web server can access.Listing 1.2 SimpleASPX.aspxSimple ASPX PageUsername:Comments:The C# version of this code can be found on the CD-ROM.Notice the four modifications to this page. First, you rename the page from SimpleHTML.aspx to SimpleASPX.aspx. The particular name of the file is not important, but the .aspx extension is very important. Your Web server detects that the page is an ASP.NET page and not a normal HTML page or other type of page because of the special .aspx extension. You create all your ASP.NET pages with this special extension.ASP Classic NoteWhat about files that end with the extension .asp? Classic ASP developers (users of versions of ASP before ASP.NET) named all their ASP files with the extension .asp instead of .aspx. You can continue to name your ASP files with the extension .asp, but they do not gain any of the new functionality of ASP.NET. Files with the .asp extension continue to be executed as classic ASP files.By default, files with the extension .asp are mapped by Internet Information Server (IIS) to asp.dll, and files with the extension .aspx are mapped to _aspnet_isapi.dll. So, both classic ASP files and ASP.NET files can happily live and work together on the same Web server.NOTEYou might want to use an extension other than .aspx for your ASP.NET pages in several situations. For example, you might have a Web site with hundreds of existing pages with names that end with the extension .htm or .html and that have already been indexed by a search engine such as AltaVista or Google. You might not want to change the extensions of these filenames because you fear that youll lose ranking in the search engines.You can, in fact, use any extension that you please for ASP.NET pages. See the first appendix at the back of this book, Migrating from ASP to ASP.NET, for details on how to do this.Second, notice that the attribute Runat=Server is added to all the form tags. For example, instead of usingto create the username form field, you use the following tag instead:The Runat=Server attribute converts these standard HTML tags into smart server-side HTML tags. When the SimpleASPX.aspx page is opened in a Web browser, the form tags with this attribute are executed on the Web server before any content is rendered to the Web browser. The Runat=Server attribute converts these standard HTML tags into ASP.NET controls.Third, notice that instead of using the NAME attribute to name the form fields, you give the form fields a unique identifier with the ID attribute. You use the ID attribute because you are no longer treating the form fields as simple HTML tags; you are converting the form fields into server-side objects.Finally, notice that you modify Listing 1.1 so that you can open the HTML form usingrather than the standardIf you want to convert any of the form fields within an HTML form into ASP.NET controls, you must use the Runat=Server attribute with the opening form tag.Notice that the Method attribute of the form tag is not used with the control version of the form tag. By default, the ASP.NET HTML Form control automatically includes this attribute.NOTEBy default, the standard HTML form tags Method attribute has the value GET. When a form is submitted with the Method=Get attribute, the form data is submitted as query string variables. Because a lot of form data cannot be passed in a query string (its browser-dependent, but typically not more than 1,000 to 2,000 characters), most people add a Method=POST to the form tag whenever they create an HTML form.The ASP.NET version of the form tag has the opposite behavior. By default, form data is posted with Method=POST. This version is nice because it saves some typing (Ive spent the past six years typing Method=POST whenever I create a form). If you really want to, however, you can override this behavior and specify Method=Get.Furthermore, notice that an Action attribute is not specified. The ASP.NET HTML Form control automatically posts back to the same page (SimpleASPX.aspx). Therefore, the server-side version of the form tag performs the same way as the original form tag, but with less typing on your part.In short, to convert a standard HTML file into an ASP.NET page, you make four modifications to the page:1.You rename the file so that the filename ends with the extension .aspx.2.You add the attribute Runat=Server to each of the form tags.3.Instead of using the NAME attribute for the form tags, you use ID instead.4.You convert the opening tag from to the simpler .Now that youve converted a standard HTML form into a smart ASP.NET form, what do you get out of it? Open the page in Listing 1.2 (SimpleASPX.aspx) in a Web browser and try submitting the form. Notice that all the form data (any text you type into the username and comments fields) is preserved between form posts. Now try to post the form over and over again. Notice that the form data does not disappear.Whenever I demonstrate a smart ASP.NET form to people, I always receive what I call the Yawn Reaction. Okay, a typical response goes, the form saves the data, but whats the big deal? Users of earlier versions of ASP inevitably respond, I could do the same thing with a couple lines of script in any case. ASP.NET和.NET框架ASP.NET是Microsoft的全部.NET框架的一部分，它包含大量的编程类，这些编程类被设计成满足任何想得到的编程需要。在下面两节中，你将学习ASP.NET如何与.NET框架配合，以及可以在ASP.NET页面中使用的语言。.NET框架类库假设你是Microsoft的决策人，再假设你必须支持多种语言，比如Visual Basic、 Jscript和 C+。这些编程语言的许多功能会有重复。例如，每种语言必须包含访问文件系统、操作数据库和操作字符串的方法。而且，这些语言包含类似的编程结构。例如，每种语言都可以表达循环和条件。尽管用Visual Basic写的条件语法不同于用C+写的条件语法，但是编程原理是一样的。最后，大多数编程语言具有相似的变量数据类型。例如，在大多数语言中，豆油办法表达字符串和整数。整数的最大和最小尺寸也许取决于语言，但是基本的数据类型是一样的。为多种语言维护这些功能需要做大量的工作。为什么要在基本的编程元素上重复投资呢？如果只创建这些功能一次并且可为每一种语言所使用，那么不是更简单吗？.NET框架类库就能达到这个目的。它包含大量的可以满足任何想得到的编程需要的类。例如，.NET框架包含用于处理数据库访问、操作文件系统、操作文本和产生图形的类。另外，它还包含更多特殊化的类，用于执行处理正则表达式和处理网络协议等任务。.NET框架还包含表达所有基本变量数据类，比如字符串、整数、字节、字符和数组。对于本书来说最重要的是，.NET框架类库包含用于建立ASP.NET页面的类。总之。你要知道在建立ASP.NET页面时可以访问任何.NET框架类。理解命名空间你可以想象得到，.NET框架非常大。它包含数千个类（超过3400个类）。好在这些类并不是堆在一起的。.NET框架的类由命名空间组成层次结构。ASP传统提示在以前的Active Server Pages 版本中，只能访问五个标准类（Response、 Request、 Session、 Application和Server对象）。而在ASP.NET中可以访问超过3400个类。命名空间（namespace）是类的逻辑分组。例如，与操作文件系统相关的所有类集中在System.IO命名空间中。明明空间组织成一个层次结构（逻辑树）。这个树的根是System命名空间。这个命名空间包含用于基本数据类型（比如字符串和数组）的所有类。它还包含用于操作随机数、日期和时间的类。类的完整的命名空间可以惟一地标识.NET框架中的任何类。例如，以下代码惟一地代表一个文件系统文件的类（File类）：System.IO.FileSystem.IO代表命名空间，而File代表具体的类。注意查看.NET框架的参考文档，可以了解.NET框架类库中标准类的所有命名空间。标准的ASP.NET名称空间ASP.NET页面可以默认地使用某些命名空间中包含的类（对于其它命名空间，则必须显式地导入）。这些默认的命名空间包含ASP.NET应用程序中最常使用的类，如下所示：System包含所有基本数据类型和其它游泳的类，比如与产生随机数和操作日期和时间相关的类。System.Collections包含用于操作标准集合类型（比如散列表和数组列表）的类。System.Collections.Specialized包含代表特殊化集合（比如链表和字符串集合）的类。System.Configuration包含用于操作配置文件（Web.config文件）的类。System.Text包含用于编码、解码和操作字符串内容的类。System.Text.RegularExpressions包含用于执行正则表达式匹配和替换操作的类。System.Web包含用于使用World Wide Web的基本类，包括表示浏览器请求和服务器响应的类。System.Web.Caching包含用于缓存页面内容的类和用于执行自定义缓存操作的类。System.Web.Security包含用于实现身份验证和授权（比如表单和Passpord验证）的类。System.Web.SessionState包含用于实现会话状态的类。System.Web.UI包含用于建立ASP.NET页面的用户界面的基本类。System.Web.UI.HTMLControls包含用于HTML控件的类。System.Web.UI.WebControls包含用于ASP控件的类。与.NET框架兼容的语言对于本书来说，我们将使用Visual Basic编程语言编写ASP.NET的应用逻辑。这是ASP.NET页面的默认语言（也是世界上最流行的编程语言之一）。尽管在本书中一直使用Visual Basic，但是你要明白：可以使用支持.NET通用语言运行时（.NET Common Language Runtime）的任何语言创建ASP.NET页面。这包括C#（发音为“See Sharp”）、Jscript.NET(JavaScript的.NET版本)和C+的受管扩展。Microsoft以外的公司已经为使用.NET框架开发了几十种语言。这些语言包括Python、SmallTalk、Eiffel、COBOL。这表示如果你愿意就可以使用COBOL编写ASP.NET页面。不管你使用什么语言开发ASP.NET页面，都需要认识到ASP.NET页面在执行前需要编译。这表示ASP.NET页面可以非常快地执行。在你第一次请求ASP.NET页面时，页面被编译为.NET类，产生的类文件被保存在你的服务器上的一个特殊的目录之下，这个目录名为 Temporary ASP.NET Files 。对于每个ASP.NET页面,在Temporary ASP.NET Files目录中都有一个对应的文件。当你以后请求相同的ASP.NET页面时，执行对应的类文件。当ASP.NET页面被编译时，它不是被直接编译为机器码，而是被编译为一种中间语言微软中间语言（Microsoft Intermediate Language, MSIL）。所有与.NET兼容的语言都被编译为这种中间语言。在浏览器实际请求ASP.NET页面以前，页面不被编译为本机机器码。此时，用.NET框架即时（Just in Time, JIT）编译器编译Temporary ASP.NET Files目录中包含的类文件，并且执行它。这个过程的神奇之处在与，它是后台自动发生的。你需要做的只是为ASP.NET页面创建包含源代码的文本文件，.NET框架会替你处理将它转换为编译后代码的艰苦工作。ASP传统提示 VBScript的情况如何？在ASP.NET出现之前，VBScript曾是用于开发Active Server Page的最流行的语言。ASP.NET不支持VBScript，这是好消息。Visual Basic是VBScript的超集，这意味着Visual Basic具有VBScript的全部功能，而且功能更多。所以，在Visual Basic 中可以使用的函数和语句更丰富。另外，与VBScript不同，Visual Basic是编译语言。这意味着如果你使用Visual Basic重写用VBScript写的代码，那么可以得到更好的性能。如果你过去只用过VBScript，而没有用过Visual Basic，也不必担心。因为VBScript与Visual Basic关系密切，所以在这两种语言之间进行转换是很容易的。注意Microsoft 在.NET框架中包含了一个有趣的工具IL反汇编程序（IL Disassembler, ILDASM）。可以使用IL反汇编程序查看Temporary ASP.NET Files目录中任何ASP.NET类的反汇编代码。它会列出类的所有方法和属性，并切允许你查看中间代码。这个工具也可以处理本章讨论的所有ASP.NET控件。例如，可以使用IL反汇编程序查看TextBox控件（位于文件System.Web.dll中）的中间代码。ASP.NET控件简介ASP.NET控件为你的Web应用程序提供用户界面的动态和交互部分。控件给出网站用户实际上看到并与之交互的内容。例如，可以使用空间创建HTML表单元素、交互式日历和旋转的广告条。ASP.NET控件可以与HTML内容和平共处。通常，用HTML内容创建网页的静态部分，而使用ASP.NET控件创建动态或交互部分。理解ASP.NET控件在HTML页面中的工作原理的最好方式是：看一个简单的Web表单页面。简单的ASP.NET页面我们先来看一个一般的HTML页面。稍后，我们将把它转换为ASP.NET页面。首先，在你的计算机上打开Notepad（记事本），输入程序清单1-1中的HTML代码。在Notepad中输入HTML页面之后，将它在inetpub/wwwroot目录中保存为SimpleHTML.aspx文件。注意在创建ASP.NET页面，一定要将它们保存在你的Web服务器可以访问的目录中。你需要将你的页面保存在inetpub/wwwroot目录、inetpub/wwwroot目录的子目录或者你的Web服务器的虚拟目录中。在保存页面之后，不要通过输入页面的文件路径在Web浏览器中直接打开它。如果你的Web服务器与Web浏览器在同一台计算机上，那么通过在浏览器的地址栏中输入页面的地址来打开页面。例如，如果页面名为SimpleHTML.aspx，在浏览器的地址栏中输入以下文本可以打开此页面： HYPERLINK http:/localhost/simplePage.aspx 对于本书来说，我假设你使用Web编辑器或NotePad创建网页。Web编辑器包含在本书配套的CD光盘中。但是，使用其它文本编辑器或Web开发环境（比如Microsoft Visual Studio .NET、 Microsoft Visual Interdev、Allaire的Homesite或TextPad）也没问题。任何可以按纯文本格式保存文件的程序都行。提示在用Notepad保存文件时，集注在Save As对话框的Save As Type框中选择AllTypes。如果不这么做，Notepad会自动地在文件名后加上扩展名.txt。防止添加扩展名.txt的另一个办法是，在保存文件时将文件名放在引号中。程序清单1-1 SimpleHTML.aspxSimple HTML PageUsername:Comments:这段代码的C#版本包含在CD光盘中。程序清单1-1中的页面包含一个简单的HTML表单，其中包括一个用户名文本域和注释文本域。例如，这个表单可以在网站上简

温馨提示:
1: 本站所有资源如无特殊说明，都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
2: 本站的文档不包含任何第三方提供的附件图纸等，如果需要附件，请联系上传者。文件的所有权益归上传用户所有。
3.本站RAR压缩包中若带图纸，网页内容里面会有图纸预览，若没有图纸预览就没有图纸。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 人人文库网仅提供信息存储空间，仅对用户上传内容的表现方式做保护处理，对用户上传分享的文档内容本身不做任何修改或编辑，并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容，请与我们联系，我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。

人人文库网所有资源均是用户自行上传分享，仅供网友学习交流，未经上传用户书面授权，请勿作他用。