TEDD/BLOG
← Back to articles
ASP.NETTips

Tip: Always use ASP.Net State Server during development

Using ASP.Net State Server during development forces everything you put in Session to be serializable — which means switching to State Server or SQL sessions in production won't blow up in your face later.

Tedd1 min read

Always use ASP.Net State Server during development

http://msdn.microsoft.com/en-us/library/ms972429.aspx Using “ASP.Net State Server” during development forces developers to use serializable-attribute on all objects stored in Session.

Reasons:

\t

  • No extra effort required by the developer.

\t

  • Changing to ASP.Net State Service or SQL session storage on a solution not developed for it requires a full and extensive test of the whole solution.

\t

  • If the server needs to be set up with round-robin or load balancing the solution already support it.

\t

  • When solution is deployed to production the default inproc (non-ASP.Net State-server) session storage can still be used.

Written by Tedd · Oslo, Norway

Follow the journal via RSS

Keep exploring

All articles →