So, I’ve always incorrectly thought that somehow, the cookie stored in asp.net was somehow tied to the Session provider in asp.net. Turns out I’m wrong. This came up because I was discussing with another engineer whether we need to bother with a Session provider since we do not use Session in our web application. That is, we don’t ever store information by saying something like:
Session[“MyKey1”] = “MyShoppingCartInfo1”;
My assumption was that somehow, the Cookie planted on the client’s browser was in lock step with the IIS server through Session and that even if we did not store Session data, we still had to hook up a Session Provider. Wrong I am.
