Best practice for user/customer repository

[Shlomi]

Hi,

Until now I used the Session("x")="y" method for saving user or
customer info throw web pages (differently for each session) like that:

Session("UserName")="Bob"

My questions:
==========

In Asp.net 1, is there another way, cleaner and structured for doing
the same thing? Something like a class and syntax like
obj_User.UserName="Bob" (Important: without the necessity to declare
obj_User in each page!).

Are they any articles on that issue in the web?

Thank You,

Shlomi

 

[OHM \( One Handed Man \)]

Ok, create the following class , this can be called from within another
class beit, page or one of your own. You should set this on session start to
the users name. So the users name call bed called CurrentUser.Name

Public Class CurrentUser

Public Shared Property Name()
Get
Return HttpContext.Current.Session("UserName")
End Get
Set(ByVal value)
HttpContext.Current.Session("UserName") = value
End Set
End Property

End Class

 

[Shlomi]

Yes, but how to avoid declaring an instance of a class in each page
that I approach?
Do I have to use session variable anyhow?

 

[Guest]

Hi,

Have you thought of using forms authentication?

Then you have available ..

HttpContext.Current.User

Wozza

 

[OHM \( One Handed Man \)]

You dont need to instantiate it, the property is shared.

 

[sloan]

Check my blog
http://spaces.msn.com/sholliday/ 10/24/2005 entry

I have a cleaner way to store objects in the SESSION variable.

I'd create an object

class UserInfo
{
public string UserName
{ get { return this.m_myname; }}

}

and use my wrapper object to store instantiations of this object.

...