It's amazing what one can find - VS.NET 2005 ASP.NET web.config schema inconsistency shows some interesting stuff
Sponsored By
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.
About Scott
Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.
About Newsletter
Hosting By
October 19, 2004 16:35
Is it actually out of sync, or is VB.Net hiding "advanced members" again?
Eric
Maybe the stateConnectionString is used for the sql connection string to the Session State database? If not, what else could it be for?
Comments are closed.