Wrox Programmer Forums
Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 2.0 > ASP.NET 2.0 Basics
ASP.NET 2.0 Basics If you are new to ASP or ASP.NET programming with version 2.0, this is the forum to begin asking questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Basics section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old April 5th, 2007, 07:55 PM
Friend of Wrox
Join Date: Oct 2005
Posts: 124
Thanks: 0
Thanked 1 Time in 1 Post
Default Upgrading ASP w/ SQLserver 2000 to ASP.NET w/2005

I have some old ASP programs w/ SQLserver 2000 databases. Now I am developing ASP.NET projects using VB 2005 and SQLserver 2005. What are the best procedures to develop and test the ASP.NET programs?

My main concerns are:
1. What do I need to test? VB 2005/ASP.NET with 2000 data? Migration of 2000 data to SQLserver 2005? VB 2005/ASP.NET with 2005 data?
2. How to minimize the transition time? What is the critical change for the end users? SQLserver 2000 to 2005 or ASP to ASP.NET?

C. Jeffrey Wang
Old April 5th, 2007, 11:30 PM
planoie's Avatar
Friend of Wrox
Join Date: Aug 2003
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts

You should have very little problem migrating a 2000 DB up to 2005. Yes, there are lots of new things in SQL 2005, but ultimately, it's still a relational SQL database engine strongly based on the 2000 model.

For the user, going to ASP.NET doesn't even need to be noticeable. Of course, if you are going to upgrade a site to ASP.NET 2.0, you should take advantage of all that it has to offer (controls and usability enhancements, etc).

I would say the biggest technical challenge to this upgrade path is the different programming style from ASP to ASP.NET. You are going from an interpreted, non-object oriented, loosely typed, script style language to a compiled, OO, strongly typed, event based language and environment. It's a pretty big technological step.

Questions to ask yourself are:
What is my level of expertise in the target environment? Should I build some simple test applications in the new environment to get a feel for how it works so I can best determine how to migrate a legacy application?

A recent wrox book that I would recommend is ASP.NET 2.0 Instant Results. It describes the construction of several applications from start to finish so you can get a good idea of how to build an ASP.NET app (versus just how to use control X and feature Y).

One thing is for sure: graduating from building apps in class ASP to .NET is a big step. It requires a whole different frame of mind. It would be very wise to just play around with .NET to get an idea of how it works before you start to migrate code to it. It's very easy to get yourself into the trap of bringing a whopping plate of spaghetti code to a .NET app and seriously detracting from .NET's capabilities.


Similar Threads
Thread Thread Starter Forum Replies Last Post
integrate asp.net2.0,sqlserver 2005 with MOSS2007 suryasimha SharePoint Admin 0 June 18th, 2007 05:16 AM
SQLserver 2000 vs SQLserver 2005 Express cJeffreywang BOOK: Beginning ASP.NET 2.0 and Databases 0 April 22nd, 2007 09:52 AM
ASP.NET 2.0 & SQL Server 2000 / 2005 Hosting NonStopMark ASP.NET 2.0 Basics 1 January 1st, 2007 02:56 AM
Unable to run script of sqlserver 2005 in 2000 prashantlakhlani SQL Server 2000 1 August 24th, 2006 10:41 AM
Upgrading to ASP.NET 2.0 Questions Aaron Edwards ASP.NET 2.0 Basics 2 December 11th, 2005 11:51 PM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.