The main problem is that there is no single great way to share session state
between ASP and ASP.NET.
But that doesn't mean you don't have options.
Here are some common ways:
* Store the data in a common database
* Pass data from page to page on the QueryString
* Store the data in cookies
* Use a 3rd party session sharing component
(Here's one:
http://www.consonica.com/solutions/d...tch/index.html)
* Use COM Interop to provide an object that both sides can access that
handles the data.
Here's an example of the latter:
http://msdn.microsoft.com/library/de...rtToASPNET.asp
Eventually you'll likely want to convert your old ASP stuff to ASP.NET.
Here's more info on good ways to do that:
http://www.able-consulting.com/dotne...iles/frame.htm
http://msdn.microsoft.com/library/de...rtToASPNET.asp
--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net
Hire top-notch developers at
http://www.able-consulting.com
"Gilgamesh" <> wrote in message
news:...
> Hi there,
> We have a legacy ASP application which we would need to continue to
> support.
> There's a need to add new functionality to the application, which I intend
> to implement it in ASP.NET if possible. The asp application is hosted in a
> secured environment with users connecting to the app using SSL. I was
> wondering if there's a way to do this without creating a separate asp.net
> web application.
>
> I appreciate any comment.
> --
> Thanks,
> Gilgamesh
>
>