ASP -> ASP.NET

[rc]

Hello,



We currently have a web site based on ASP and SQL Server. The hosting
company currently runs the site on a Windows 2000/ IIS 5.0 hosting plan and
everything works fine.



Our current site does not use any 3rd party components and the DB connection
string is as follows:



"Provider=SQLOLEDB.1; Network Library=dbmssocn;Password=foo;User
ID=foo;Initial Catalog=foo;Data Source=12.345.67.890"





The current hosting plan does not support .NET, but the company does offer
..NET hosting plans.



Ideally, I would like to move the site, verbatim, to the .NET environment
and slowly start replacing/developing with ASP.NET.





If I have them move the site, should I anticipate any problems running a
native ASP application in a .NET environment?





Any insight would be helpful.



Thank you

 

[GrantMagic]

ASP runs fine in a server able to run .NET.
The .NET framework consists of additional functionality and classes that are
not available to traditional ASP.
ASP will run fine in these conditions, it just won't use what it can't.

Furthermore, when you start migrating your site over to ASP.NET, you can
migrate pieces at a time.
It shouldn't be a problem, authorisation may differ among how .NET and
traditional ASP works (with regard to access levels and cookie information),
but during migration, asp authorisation can be preserved and run parallel
with the newer .NET authorisation methods.

To cut along story short - once again - there should be no problems.

 

[Guest]

Yes, you would basically need to rewrite most everything. ASP .NET is not
really like classic ASP at all.

 

[Kevin Spencer]

ASP and ASP.Net are 2 entirely different ISAPIs, and the only environment
they share is the file system. You can certainly run them side-by-side.
Sharing data between them will be problematic, though, for this very reason.
You have to either pass shared data from one app to the other in any of
various ways, or use a common data store, such as a database.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
I get paid good money to
solve puzzles for a living

 

[Hans Kesting]

ASP runs fine in a server able to run .NET.
The .NET framework consists of additional functionality and classes
that are not available to traditional ASP.
ASP will run fine in these conditions, it just won't use what it
can't.
Furthermore, when you start migrating your site over to ASP.NET, you
can migrate pieces at a time.
It shouldn't be a problem, authorisation may differ among how .NET and
traditional ASP works (with regard to access levels and cookie
information), but during migration, asp authorisation can be
preserved and run parallel with the newer .NET authorisation methods.

To cut along story short - once again - there should be no problems.

"no problems" might be a bit *too* short. I think it is best to view the ASP
and ASP.Net sites as separate applications, where you require non-trivial
effort to synchronize both. For starters, you can't share Session state!

How much effort it will be depends on the nature of the application
to migrate (if you don't use session-state at all, then it might be easy,
if you depend on it, it's more difficult)

Hans Kesting

 

[GrantMagic]

right you are HAns, it definately depends on the project,
appologies for the hasty reply