I'm a relative newbie to ASP.net but I'm relatively familiar with ASP classic and I have a reasonable understanding of object oriented languages such as Java. (and C# seems very similar to me, so that's what I've been using in my early ASP.net development).
I'm quite happy with most of my ASP.net learning, but there's a big hole in my understanding - and I'd like some lovely experts to come along and explain some things to me in order to fill this chasm.
Right, lets say I have a web page for some customers and I want to hold some details about the customer who is logged in. Some of these details will be from what the user has supplied, like userid and password, and some of the details will be from the database which holds all the other details about the customer of course.
So, in my mind I'd like to instantiate a customer object, in which I'd hold various details. If the customer was to buy anything, I'd attach a shopping cart object and then some "shopping cart item" objects. Make sense?
Anyway, I can't understand how on earth this sort of thing works with ASP.net. I can create my customer object and I can call methods etc from an ASP.net page, but then what if i want to access my customer object on the next ASP.net page? How do i do that? I can't go an re-create the customer object can i. (well I can, but that's obviously a bit silly) Am I mean to keep some kind of reference to something? I just don't quite get it. Is it anything to do with Server Objects? (and if so how?)
So, I'd love an explanation. I've googled for many many hours and read (skimmed) a couple of books, but I still don't feel like I quite get this. I also realise I could hold this kind of data in a Session object, but that seems wrong. Surely the whole point of this is to use an object oriented methodology?