Why should Everyone convert their Old Active Server Pages 3.0 to the Newer Active Server Pages .NET Framework 2.0? Well, using the new Visual Studio 2005 IDE will show you just how EASY it is having the HTML and the Source Code Separated!
There are several reasons that we will discuss and demonstrate on this page. First, we need to identify the ASP 3.0 Obect Model and Then the Shortcomings that were associated with creating ASP 3.0 web pages. I have presented everything in image form thinking that even non-technical people could follow the logic of how to do something like this!
The Active Server Page 3.0 Object Model
The Active Server Page 3.0 Shortcomings
-- Interpreted and Loosely Typed Code
-- Collaboration with multiple developers is Difficult
-- Limited Development and Debugging Tools
-- Server Affinity when maintainig Session State
-- Obscure Configuration Settings
-- Code Required for Postbacks and Multi Browser Support
The Active Server Page .NET 2.0 Improvements
-- Compiled and Maintainable Code
-- Separation of Code from HTML, Collaboration Easier
-- Graphical Development Environment, Like that of Windows
-- Cluster Friendly State Management
-- XML Based Configuration Files
-- Automatic Handling of Postbacks and Multi Browser Support
-- ASP.NET 2.0 is FUN!
I created a Visual Studio 2005 Solution file called Intro1 containing one Project called C:\ASP.NET\Intro1\ with an ASP 3.0 application called Products-ASP.asp. I used the Microsoft Access Database Northwind for this Introduction application first using ASP 3.0 then ASP.NET 2.0.
Notice the Products-ASP.asp file extension naming convention refers to original ASP 3.0.