Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Reading conflicting opinions on using SQL session state vs custom db table in MVC to store user data across page requests?
What are the advantages and disadvantages to each method? Why should I pick one method over the other.
So far it seems a custom db table is the best solution because it doesn’t time out, plus it would be strongly typed using the Entity Framework.
Am I missing something?
Seems like SQL session state is the way to go if you need your data to expire, otherwise a custom database table seems like the way to go. Especially when using entity framework, less work to setup and you get a strongly typed object. No Session[“VarName”] stuff..