Brad,
Thank you for your response.
Just to clarify, the ASP application is along several .NET 1.1
applications which all reside in the same default app pool configured
for 1.1. These 1.1 applications encounter no problems with the ASP
application, which is what led me to believe that the data cannot be
shared across the application pools.
Perhaps I could post the info using encrypted querystrings, but I'd
like to keep that as the last resort; unless of course it is my best
and/or only option?
Regards,
Michael
Brad Roberts wrote:
I'm a little confused about the reference to "1.1" but...your suspicion is
correct. The applications are separate and cannot share the session cookie.
However, if there is information you want to POST to the .NET application
from the ASP app then that would work.
--
Brad
"Software is like melted pudding..."
"te***********@gmail.com" wrote:
Hello,
We are currently migrating our system from asp to asp.net. Our main
page is still using classic asp. When a user logs in to the system, a
cookie is created with the user info. The user then clicks a link;
which is a seperate application written in asp.net 2.0.
ie. http://my.application.com/ (asp)
http://my.application.com/new2.0application (asp.net 2.0)
However the new application cannot find the cookie created from the
login (asp).
My only theory is that cookies are not accessible between application
pools, as the asp.net 1.1 applications read the login cookie just fine.
Any insight into this matter would be greatly appreciated.
Thanks in advance.
Regards,
Michael
