Asp+ It includes the configuration of the running platform, the creation of Pagelet, the use of new ado+, the use of new datasets for data access, the transformation of HTML forms to DataList, and the use of many other new server-side controls ... What are you waiting for? Now feel asp+ 's new charm! ）
Since Microsoft announced asp+ at the July 2000 Professional Developers ' conference, one of the same issues has plagued many newsgroups and discussion forums: "What do I need to do to convert existing Web applications from ASP to asp+?" A spokesperson for the professional developer's meeting said: there is no need to make major changes to the code, and the entire conversion process is not too difficult. Is that so? In this article, we will explore exactly.
To run the alpha version of asp+, you need to:
Windows Professional Server, or Advanced Server
IIS5.0
Internet Explorer5.5
.. NET Framework runtime (. NET Framwork Runtime)
(future releases of asp+ will be available on Windows NT and 9x)
If you are an ASP developer, the techniques you currently use such as VBScript will easily be converted to visual Basic. NET to asp+ page for you
Write code. You may also use other languages, such as c#,managed C + + or COBOL. In this article, I'll describe the detailed steps required to upgrade a small Web application from ASP to asp+. The sample code uses visual Basic. Net.
Although ASP and asp+ can co-exist with each other, we choose to migrate the entire site to asp+. The migration is a sample site that is used to demonstrate entry-level Web development. We feel that this site represents a significant portion of the current network of typical small and medium sites. The site URL is: http://www.codejunkies.net/eVille/, it is a virtual enrollment site, enrolled students will learn it-related courses. The site is built on the Windows2000 server, driven by the Access2000 database, uses VBScript, client JavaScript, and ASP3.0, and does not use COM.
On the same Web server running IIS5.0, ASP and asp+ are designed to support running in parallel (the final release version will support other versions of IIS). This means that we can migrate the entire site one page at a time. The original page can still run under ASP3.0, and the new page will be converted to use asp+ server controls and functions.
The first step we need to make is for IIS to be able to use Default.aspx as a valid default file. This step is fairly straightforward, in Internet Service Manager:
* Open the ' Properties ' dialog box in the IIS virtual directory
* Click the ' Add ' button in the ' File ' tab
* Input default.aspx
* Click ' OK ' two times
The Eville site used for the example does not use COM, so all data access is done through ADO in ASP or include files. One of our initial goals is to transform ADO into ado+ to get better results from ado+ Managed provider. Asp+ supports the use of traditional ADO, but migrating to ado+ will benefit more. Let's say: Get more than one table (table) from a single dataset, faster execution speed, and bind data to server controls. Data access in asp+ pages can be done through ado,ado+ or SQL Managed provider. Since the sample site is not using SQL Server and we want to optimize execution, ado+ has become our best choice.
Every page of this site involves data access, so it will make up the largest proportion of the conversion project. Basically, each page must make some code modifications to get and display the data needed for that page. There is a connect.inc file in the Eville structure that contains the ADO connection code, and it is available on every page. The connection has been built and ready to use. Because the process of connecting to a database and binding to a asp+ data control is done by a new Page_Load event in asp+, we now have to take a slightly different approach.
