We've experienced problems with our webapplication in Azure. The main problem is that the Session State is somehow lost. This happens only sometimes, not always. Who can help me?
In order to run the webapplication in Azure, I've made a reference to AspProviders.dll (from the azure sdk C:\WAPTK\Labs\WindowsAzureDeploymentVS2010\Source\Assets\AspProviders\bin\Debug\AspProviders.dll), created a Connection String to the Azure Table Storage
(the session state is saved in the Table Storage) and added the web.config:
I believe the AspProviders.dll Assembly is a remainder of a Samples solution. All I know is that we experienced a lot of problems with it in production and we decided to use SQL Azure a datastore for session state.
The System.Web.Providers assembly was released a couple of weeks ago (or is it months already?? ;-)) and is newer than the AspProviders.dll. As it turns out, there's no TableStorageSessionStateProvider in System.Web.Providers anymore, so I figure that storing
session state in SQL Azure is the recommended way to go.
Maybe, with the latest updates of Windows Azure Storage (enabling Upsert for instance), the TableStorageSessionStateProvider will find it's way into the System.Web.Providers assembly in the future, but this is plain speculation.