User-46109667 posted
As ASPState In-Memory introduced, am migrating the sql server session state to ASPStateInMemory.
Our website has multiple application hosted under single site and all applications need to share the same session from the sql server db. The current hosted website uses sessionstate mode as sqlserver and all applications are grouped with a application name.
So there is no problem in current structure.
<sessionState allowCustomSqlDatabase="true" mode="SQLServer" sqlConnectionString="xxxxxx;Application Name=SessionTest;" timeout="180" cookieless="false"/>
As I tried to migrate to ASPStateInMemory (Microsoft.Web.SessionState.SqlInMemoryProvider) the session state is not getting shared by the applications. A new session is getting created for every application.
My website structure would be like:
|- RootWebsite(having the login page)
|-application1
|-application2
|-application3
Note:
We have created the ASPStateInMemory database, and added SqlInMemoryProvider to our application with .net framework 4.5.
The problem is all the applications are not sharing the same session db.
Can someone help me to handle multiple applications using new In-Memory structure?