I would recommend that you pick isolated sections of your application that
do not have session or application dependencies and convert them to asp.net
pages, and only do this when you need to update a part of your application
or bug fix. Migration from a working application especially given that asp
is still technically a supported product and you are running a live app
doesn't really offer you anything other than additional work.
Can you run a compiled dll in asp - yes - would I do it - only if I couldn't
find a more appropriate solution.
http://msdn.microsoft.com/library/de...mblyforcom.asp
--
Regards
John Timney
ASP.NET MVP
Microsoft Regional Director
"JHowell" <JH*****@discussions.microsoft.com> wrote in message
news:57**********************************@microsof t.com...
We have a large web based internal app written in classic ASP running
against
a SQL Server2000 database (!00+ tables, up to ten million rows in a dozen
of
the tables). We would like to begin a staged port of the application by
applying the 1.1 framework to the database server and then compiling a
.dll
that will use the sqlclient connection object, which can then be called
from
the classic asp pages.
Is this a feasible idea? Or, perhaps can the calls be made directly to
to
System.Data.SqlClient from the asp pages if the frameork is installed in
the
IIS server?
Thoughts?
Thanks in advance --Jim