Is it necessary to create ASP.NET 4.0 SQL session state database, distinct from existing ASP.NET 2.0
Posted
by Chris W. Rea
on Stack Overflow
See other posts from Stack Overflow
or by Chris W. Rea
Published on 2010-05-27T15:01:59Z
Indexed on
2010/06/07
14:22 UTC
Read the original article
Hit count: 287
Is the ASP.NET 4.0 SQL session state mechanism backward-compatible with the ASP.NET 2.0 schema for session state, or should/must we create a separate and distinct session state database for our ASP.NET 4.0 apps?
I'm leaning towards the latter anyway, but the 2.0 database seems to just work, though I'm wondering if there are any substantive differences between the ASPState database schema / procedures between the 2.0 and 4.0 versions of ASP.NET. Thank you.
© Stack Overflow or respective owner