Question

I ‘m writting an application in ASP.NET MVC. Basically I have some pages which require user authentication. Upon user logon, I keep the user row in a session. So in my controller I can access to the user.ID without making extra queries.

When project is in debug mode I can only change things in the views. Not in the controller.

If I ‘m not debugging, I can build the solution, and see the changes I made without running the project (with F5). BUT, it looses all session variables I have.

So basically for every no-matter how small change in the controller, I have to logoff, logon to see my changes.

Are those normal behaviours?

Answer 1

Like Dan stated, this is normal behavior. To make it easier (and slightly more robust) is to change your code slightly. This is of course assuming that you are storing more than just the User ID in session since you can access the User ID via Controller.User.Identity.Name when they are authenticated. So you perform the lookup of the additional data in the session object and if it doesn’t return null then use it. If it does return null, then look up the additional information again based on the User ID and store it in the session again. This is the approach I take for storing information from Active Directory and it works great.