Last post Dec 30, 2009 09:16 AM by stiletto
Dec 14, 2009 10:51 AM|lax4u|LINK
I’m trying to share session between ASP.NET application and SharePoint. We are maintaining the Session in SQL DB. Since, .net cannot share session object between two .Net applications we have to hack Session SQL stored procedures to achieve the goal. (other
than this we also have same machine key for both applications).
In ASP.NET application I have a C# object “GG.BusinessObjects.Customer”, and I put that object in Session. The SharePoint site does not know anything about this assembly, I’m not sharing this assembly with SharePoint. Now, my question is when a user browse
to SharePoint site, how session object will get de-srailize because SharePoint does not know anything about “GG.BusinessObjects.Customer”?
I want to know how sharepoint will behave.
1> Will SharePoint throw exception?
2> Will SharePoint skip this object and de-serialize other known objects?
3> In SharePoint, If I have Session.Remove(“Customer”) statement, will it work?
Dec 23, 2009 09:42 AM|stiletto|LINK
IIRC, it won't be deserialized until you try to rebuild it so you shouldn't have any problem...
Try it and see what happens...
Dec 30, 2009 12:24 AM|lax4u|LINK
well the appllications are already buillt.
Dec 30, 2009 09:16 AM|stiletto|LINK
I meant that the object was rebuilt in memory...