ASP to ASP.NET?
Yeah dude. Plan on a complete port over, if you want to do it right.
If you dotNet code has references to ADODB, then you're barking up the wrong
tree.
(which is one of many bad things the upgrade wizards do)
I'll start you off with this tidbit.
NUMBER 1 THING NOT TO DO IN ASP.NET
Loop over recordsets and create html code.
Asp.Net has controls which you bind data.
asp:repeater
asp:GridView (2.0)
asp:dataGrid(1.1)
are examples.
DO NOT LOOP OVER RECORDSETS AND CREATE HTML CODE.
Good luck.
"Jeffrey" <cj*******@gmail.comwrote in message
news:9F**********************************@microsof t.com...
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?