![Mark Rae [MVP]](./core/images/default/default_avatar_large.png "Mark Rae [MVP]"){kind=avatar}
"egsdar" <egsdar@discuss ions.microsoft. comwrote in message
news:6A834615-9B38-4129-931B-9C9114682E26@mi crosoft.com...
OK, first things first: ASP.NET is *TOTALLY DIFFERENT* from ASP Classic. If
you're just moving from ASP Classic to ASP.NET, the worst mistake you can
make is to imagine that ASP.NET is the "next version" of ASP Classic. It
isn't - not even close...
As a general rule, there is no point whatsoever in even trying to "migrate"
your ASP Classic code to ASP.NET because the two systems share almost no
common ground. Microsoft published a migration tool with the very first
release of ASP.NET back in 2002, but it was an unmitigated disaster...
The best advice I can give you is to use this learning process as an
opportunity to re-engineer your ASP Classic app from the ground up and don't
even try to migrate. I would suggest that you get a copy of this:
and work your way through it from beginning to end. It will cover everything
you need to know.
Presumably, that's not your real connection string? I.e. you haven't just
published your database access credentials on a public forum...?
Also, what version of MySQL are you using? That will make a difference in
determining which connectivity method you use. If you're using version 5.x,
then you can take advantage of the native .NET data provider which means
that you don't need to use ODBC / OleDb:
--
Mark Rae
ASP.NET MVP
news:6A834615-9B38-4129-931B-9C9114682E26@mi crosoft.com...
Hello, I have a code that I did in ASP and need to migrate to ASP.Net.
This
is my code in ASP 3.0:
This
is my code in ASP 3.0:
you're just moving from ASP Classic to ASP.NET, the worst mistake you can
make is to imagine that ASP.NET is the "next version" of ASP Classic. It
isn't - not even close...
As a general rule, there is no point whatsoever in even trying to "migrate"
your ASP Classic code to ASP.NET because the two systems share almost no
common ground. Microsoft published a migration tool with the very first
release of ASP.NET back in 2002, but it was an unmitigated disaster...
The best advice I can give you is to use this learning process as an
opportunity to re-engineer your ASP Classic app from the ground up and don't
even try to migrate. I would suggest that you get a copy of this:
and work your way through it from beginning to end. It will cover everything
you need to know.
set conn=server.Cre ateObject ("ADODB.connect ion")
conn.Open ("Driver={My SQL ODBC 3.51
Driver};SERVER= localhost;DATAB ASE=proyectos;U ID=root;PWD=411 6734")
conn.Open ("Driver={My SQL ODBC 3.51
Driver};SERVER= localhost;DATAB ASE=proyectos;U ID=root;PWD=411 6734")
published your database access credentials on a public forum...?
Also, what version of MySQL are you using? That will make a difference in
determining which connectivity method you use. If you're using version 5.x,
then you can take advantage of the native .NET data provider which means
that you don't need to use ODBC / OleDb:
--
Mark Rae
ASP.NET MVP
