Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InProc throws NRE in 2.0.0 #94

Open
mellamokb opened this issue Jul 13, 2023 · 2 comments · Fixed by mellamokb/AspNetSessionState#1 · May be fixed by #98
Open

InProc throws NRE in 2.0.0 #94

mellamokb opened this issue Jul 13, 2023 · 2 comments · Fixed by mellamokb/AspNetSessionState#1 · May be fixed by #98

Comments

@mellamokb
Copy link

Just noticed the new version dropped, I get an NRE in the 2.0.0 version due to this line, while using InProcess mode.

var skipKA = config["skipKeepAliveWhenUnused"];

Because config is null in the case of InProc. Simple solution was to add null coalesce operator on the indexing.

@eduardo-publi
Copy link

To people that is just want to use performance Benefits from this Async Session State Module using InProc, while fix #98 doesn't come as a package version 2.0.0.1, you can just add InProc as a custom provider, so it will not throw a NRE

<sessionState mode="Custom" customProvider="FakeCustomInProc">
  <providers>
    <add name="FakeCustomInProc" skipKeepAliveWhenUnused="false" type="Microsoft.AspNet.SessionState.InProcSessionStateStoreAsync, Microsoft.AspNet.SessionState.SessionStateModule, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
  </providers>
</sessionState>

@kim3er
Copy link

kim3er commented Nov 15, 2023

Thank @eduardo-publi, great workaround. Hoping for a release with the hotfix in it though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants