Why do object/session expiration events stop being delivered to a Web application after upgrading from ASP.NET 2.0 to ASP.NET 4.0?

#1
I recently upgraded my web application to target the .NET 4.0 framework instead of .NET 2.0. My application properly received and handled session expiration events prior to the upgrade, but the events are no longer firing after the upgrade.
 
#1
Event delivery can be disrupted after transitioning to ASP .NET 4.0 if the ScaleOut session provider for ASP .NET 2.0 is used under the .NET 4.0 runtime. Confirm in your web.config's <sessionState> element that version 5.0.0.0 of the soss_storeprovider assembly is being referenced.
Code:
<sessionState mode="Custom" customProvider="SossStoreProvider" cookieless="UseCookies" >
  <providers>
    <add name="SossStoreProvider"
         type="Soss.Web.SossStoreProvider, soss_storeprovider, Version=5.0.0.0, Culture=neutral, PublicKeyToken=a1ec0b86f746a476"
      />
  </providers>
</sessionState>
 
Top