Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Apr 29, 2012 06:41 PM|LINK
Thank you again Brock! I will try to stick to my previous framework attitude and avoide session as well, I will leave them as a possibility with SQL Server (or in-proc based on the needs) for plugging in third party stuff wich uses session.
On my classic asp framework (without sessions) I had a db call on each page to check user identity against the cookie and retrieve the permission.
Now with asp.net, even if you have to customize a lot to obtain what you really want, I must say it gives you infinite possibility, it's funny, Visual Studio IDE is astonishing... well I'm feeling like a baby in candy store :) The risk is that you gather
so much infos that your mind is next to blow up :) But I think this phase of gathering is well worth before even starting to code, to start in the right direction and avoid having to recode the core of your framework later (as far as this is possible)