Session Object

[Guest]

I am trying to save private information such as user id and password from one
application and send it to another application. I tried saving the
information in the Session Object and when the user goes to a from one
application and then redirecting them to the different application it does
get the information stored in the session object. Is there any way to store
an information in one application and be able to access it to a different
application. I do not want to pass it via the web page query string.

thanks in advance...

 

[Marina]

Sessions are unique to each application. You will need to find a way to
place the data in a central place, where each application can access it
(e.g. a database). Of course, you would probably still need to pass some
sort of key across (so the 2nd app can do a lookup of info) via something
like query string, or a post.

 

[Hermit Dave]

well session object is specific to the application its under. it cannot be
shared between applications.
if users are uniquely identified in the applications and have access to a
common database then i would potentially use database to channel the data.
if the user identifier is the same then i would save the value in database
table (say serialise the object and the user reference) and then extract it
from other end.

also you could use something like a web service in one getting the data into
second app. or something like a remoting app which can talk to both and
channel the data as required.

hope this help...

--

Regards,

Hermit Dave
(http://hdave.blogspot.com)

 

[Jeff B]

Angel,

You could store the information in a database, and then retrieve it from the
other application.

Is that what you were looking for?

Jeff B
(e-mail address removed)

 

[Steve C. Orr [MVP, MCSD]]

You might consider storing the value in a common database, or you might
consider posting (via hidden field) to the page in the other app, although
the current version of ASP.NET doesn't make this as easy as it should be.

 

[Kevin Spencer]

Web Service? Database? File? I'm sure there are many other ways. The basic
principle is this: You have to put the data where both apps can get to it.
And that is NOT in either app's memory.

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

 

[Steve C. Orr [MVP, MCSD]]

Different applications just don't share memory. In fact, that's pretty much
the definition of an application.
So if you want them to share memory then you should make them one
application.
Assuming you keep them as separate applications you'll need to pass data
between them manually through any resource that they can both access.

--
I hope this helps,
Steve C. Orr, MCSD, MVP
http://Steve.Orr.net