It's amazing what one can find - VS.NET 2005 ASP.NET web.config schema inconsistency shows some interesting stuff

October 19, 2004 7:41 AM Comments [2] Posted in ASP.NET

I'm working on some ASP.NET 2.0 stuff with 2.0 Beta 1 Refresh, and I noticed something. 

The web.config from a VB ASP.NET app is on the left.  The web.config from a C# ASP.NET app is on the right. Here's some thoughts:

  • We know the customProvider will allow one to write their own SQL Session Store.  This is known, but not documented yet.
  • lockAttributes is new. Not sure what that's about.
  • On the right, the C# web.config XSD is out of sync with the VB.NET web.config XSD, and we see a few new attributes.
    • regenerateExpiredSessionId - This new attribute will force a re-gen of any old session ids. Previous versions of ASP.NET would start a fresh session with the provided id remaining the same.
    • allowCustomSqlDatabase allows you to have more than one ASP.NET Session State database per box, and each Application can be assigned to one by specifying Initial Catalog= or Database= in the strangely missing sqlConnectionString attribute.

Comments [2]
« Team America: World Police/Nerd Dinner | Home | SellsCon 2004 »
Tuesday, October 19, 2004 12:35:53 PM UTC
Is it actually out of sync, or is VB.Net hiding "advanced members" again?
Eric
Tuesday, October 19, 2004 2:53:15 PM UTC
Maybe the stateConnectionString is used for the sql connection string to the Session State database? If not, what else could it be for?
Ryan Rinaldi
Comments are closed.
Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer’s view in any way.