MBR IT/.NET 247 : Sharing ASP 3.0 code with .NET on ASPFriends.com 'aspngmigrate' list

Sharing ASP 3.0 code with .NET

Messages

Related Types

This message was discovered on ASPFriends.com 'aspngmigrate' list.
Responses highlighted in red are from those people who are likely to be able to contribute good, authoratitive information to this discussion. They include Microsoft employees, MVP's and others who IMHO contribute well to these kinds of discussions.

Steve Shier

We have a client who has a site built in ASP 3.0. We would like to build
newer pages in .NET but would like to use the application variable data that
is in the global.asa file on the ASP 3.0 code - this contains a lot of
cached database data and there are administration pages for updating this
quasi-static data as well. Clearly we could reload all the application
variable data in global.asax, but this would make updating the two sites a
pain in the neck and would of course consume more memory on the box.

Q1. How do you access Application("myvariable") in global.asa in an ASP 3.0
site from a .NET site (either from global.asax or mypage.aspx) on the same
server?

Q2. Are there any serious performance or runtime issues with having a .NET
site access an ASP 3.0 site's variables?

Steve Shier
Managing Member, Senior Consultant
Kubera Consulting, LLC
641-472-0595
Click here to reveal e-mail address
http://www.kuberaconsulting.com

Reply to this message...

Brian Bilbro (VIP)

----- Original Message -----
From: "Steve Shier" <Click here to reveal e-mail address>
To: Click here to reveal e-mail address
Sent: 11/10/2001 6:10:00 AM
Subject: Sharing ASP 3.0 code with .NET

>Q1. How do you access Application("myvariable") in global.asa in an =
ASP 3.0
>site from a .NET site (either from global.asax or mypage.aspx) on the =
same
>server?

I came across this problem with an application that we were updating and =
it is developed in ASP 3.0 but we wanted to do new code in .NET. :) =
What we ended up doing was just migrating the ASP 3.0 code to .aspx =
pages...we didn't try to convert ADO to ADO.NET, etc...we justed used =
COM interop to communicate with the ADO code...we figured this would get =
us to start using ASP.NET and then we can convert the classic ASP code =
in ASP.NET type (e.g. using ADO.NET instead of ADO, etc...) during down =
times in the project.

Having said that, I did look into the issue of cross communication and =
few things came to mind.

1. Create a COM component to communicate to the Application and Session =
objects. Register this COM component with .NET COM interop and use that =
to communicate to the app and session objects.

or

2. Have the .NET pages do some server-side HTTP calls to communicate to =
ASP pages (and thus ASP objects, etc...)

option #1 didn't seem to bad...option #2 seemed like a total hack.

>Q2. Are there any serious performance or runtime issues with having a =
NET
>site access an ASP 3.0 site's variables?

Never got to do any testing since we are migrating the existing .asp =
pages into .aspx pages (we're not rewriting the code...we're just doing =
what is minimal to get it run in a .aspx page so that we can just use =
the .NET application and session object and remove ASP out of the =
picture).

HTHs,
Brian

Reply to this message...

MBR BootFX
Best-of-breed application framework for .NET projects, developed by Matthew Baxter-Reynolds and MBR IT

	Copyright © Matthew Baxter-Reynolds 2001-2008. '.NET 247 Software Development Services' is a trading style of MBR IT Solutions Ltd.
	Contact Us - Terms of Use - Privacy Policy - www.dotnet247.com