On Wed, Jun 11, 2008 at 5:49 PM, Rob Mensching <[EMAIL PROTECTED]> wrote: > Interesting, didn't know the SiteId was used in farm settings. Leave to the > IIS team to take something that had no meaning and assign meaning to it > later. <sigh/>
I did some poking around and found the following.... When you run "aspnet_regsql -d test -S localhost -E -ssadd -sstype c" to create the ASP session state tables and stored procs, you'll see that the "dbo.ASPStateTempSessions" table has a SessionId column. You'll find that System.Web.SessionState.SqlSessionStateStore has a method called InitSqlInfo() that calls the dbo.TempGetAppID stored procedure to get the "_appSuffix" value, which is later used as part of the SessionId. Notice the parameter "appName" to this stored procedure is HttpRuntime.AppDomainAppIdInternal (which is an internalized AppDomainAppId). This (drum roll) does contain the site id. Here's the value of HttpRuntime.AppDomainAppId from my XP 5.1 IIS server for a test page I have: HttpRuntime.AppDomainAppId is /LM/W3SVC/1/Root/vars "1" is the site id value from the metabase. This means that servers in a farm must have the same site id if they want to share the same sql-based ASP session state provider. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
