外文翻譯---從經典asp到asp.net

1、Moving from Classic ASP to ASP.NETABSTRACTASP.NET is Microsoft new offering for Web application development, innovation within ASP.NET have resulted in significant industry popularity for this product. Consequently there

2、 is an increased need for ASP.NET education. The Web Application Development is a third year undergraduate course. To meet the demands of both industry and students, we have changed the focus of this course from Classic

3、ASP to ASP.NET. This paper reports this move. The significant features of ASP.NET and the motivations for this move are discussed. The process, the problems encountered, and some helpful online learning resources are des

4、cribed.Key wordsWeb Application Development, Classic ASP, ASP.NET, Move, VB.NET1. INTRODUCTIONASP.NET is not just a new version of ASP. It provides innovation for moving Windows applications to Web applications. Web serv

5、ices and the .NET framework have made the vision of the Web as the next generation computing platform a reality. With server controls, Web forms and “code-behind”, we can develop a Web application by using a complete obj

6、ect-oriented programming (OOP) model. This increases the popularity of ASP.NET in industry. The industry project is the final course of the Bachelor of Computing Systems (BCS) degree at UNITEC, in which students undertak

7、e a real-world project. We have observed a rapid growth of ASP.NET related industry projects in our school. The Web Application Development (WAD) paper is a third year undergraduate course. It was originally offered usin

8、g ASP 2.0 and ColdFusion. To meet the demands from both industry and students, we have changed the course content to cover ASP.NET, Visual Studio.NET (VS.NET) and ColdFusion. This change commenced with the first semester

9、 of 2003.This paper will examine the features of ASP.NET and explain why these are unique. The motivations for moving to ASP.NET are discussed by analyzing the current situation of ASP.NET related to industry projects in

10、 our school, analyzing the results of short surveys on students, and analyzing whether ASP.NET is a better tool for teaching. Problems encountered during the move are also discussed and some of 2the problem of communicat

11、ing across the Internet and across corporate firewalls without resorting to proprietary solutions that require additional communications ports to be opened to external access. In addition, URI (uniform resource identifie

12、r) and UDDI (Universal Description Discovery and Integration) are used for remote components references instead of registry entries.2.2. DevelopmentASP.NET integrates seamlessly with VS.NET IDE. VS.NET includes built-in

13、support for creating and modifying content. This unifies the ASP/VB programming models for the developers. Instead of opening multiple IDEs (as with Classic ASP platform), developers can open a single IDE and do all thei

14、r work from a clean, consistent interface. VS.NET is equipped with powerful debugging environment. This means that the powerful debugger for Windows applications is now available to debug Web applications as well. ASP.NE

15、T enables programmers to take advantage of the OOP model, for example, code sharing. Under OOP model, one of the most common ways to achieve code sharing is inheritance, which is not available in Classic ASP. Since compl

16、ete OO features are supported in ASP.NET, developers can transfer their OO design smoothly into ASP.NET code, enabling a software company to keep their Windows application development styles, with which they are familiar

17、, in Web application development; and also they can convert their Windows applications into Web applications without major modifications. ASP.NET’s improved state maintenance features enable us to provide users with Web

18、applications that are richer and faster than Classis ASP (Olges,2002). ASP.NET supports advanced session state management. There are two major problems with session management in Classic ASP: session objects are stored i

19、n the Web server memory and session IDs are stored on the client computers as cookies. These prevent session management from being efficiently implemented. ASP.NET solves these problems in two ways: it provides a “cookie

20、less” option for session objects so that a session ID can be passed via URL; it provides three different session modes (in process, state server, and SQL Server), so that a session object can either be stored on the Web