Can a session be maintained across solutions/projects?

[jgill442]

In ASP.NET, can we maintain client 'sessions' across seperate .NET solutions and/or seperate projects? We're trying to avoid having to place cookies on the client w/ session login credentials or passing login info in URL's.

In other words, can 2 seperate .NET projects or solutions that share seperate memory space in IIS pass session info across to one another?

 

[Isadore]

jg: this may help

How to Share Session/Application State Across Different ASP.NET Web Applications

http://www.asp101.com/articles/jayram/sharestate/default.asp

This article gives the details of how to share single Application/Session state across different ASP.NET web application projects developed. This is required for web applications developed separately for the sake of
modularity and require integration into a single website at a later stage.

It is better to develop each module independent of other. If there is information that needs to be shared across modules, it can be achieved through database and/or Session/Application variables, depending on the
requirements. With Visual Studio, each new ASP.NET web application project creates a new virtual directory. This means creating separate Session/Application state for each module/application. Drawback of this approach is there is no way to share same Session/Application across these
different modules developed for same website.

found it over at .dotNET247