Question

I am learning some good code practice that’s why i was going through some code, some thing i could not understand in it. It has made property in a separate class for each entity like in userClass it has property

  #region public properties

    private int uid;
    public int userId
    {
        get { return uid; }
        set { uid = value; }
    }

    private string uName;
    public string userName
    {
        get { return uName; }
        set { uName = value; }
    }

    private string pwd;
    public string password
    {
        get { return pwd; }
    //    set { pwd = value; }
    }


    private string uAddress;
    public string userAddress
    { 
        get { return uAddress; }
        set { uAddress = value; }
    }


    private string fName;
    public string firstName
    {
        get { return fName; }
        set { fName = value; }
    }

    private string lName;
    public string lastName
    {
        get { return lName; }
        set { lName = value; }
    }

    private string uPhone;
    public string userPhone
    {
        get { return uPhone; }
        set { uPhone = value; }
    }

    private string uMobile;
    public string userMobile
    {
        get { return uMobile; }
        set { uMobile = value; }
    }

    private int secretQuestion;
    public int securityQuestion
    {
        get { return secretQuestion; }
        set { secretQuestion = value; }
    }

    private string userAnswer;
    public string answer
    {
        get { return userAnswer; }
        set { userAnswer = value; }
    }

    #endregion

and from the business logic class it uses the property instead of using directly any entity’s attribute name, but i am confuse whats there need to make a property like this?

other then this it has got enums for database column name which has a clear reason behind this that if in near future we have to change the database table’s fields name then we don’t have to change through out the whole business logic class and we can make changes to enum directly, But what is there use of creating property like this please elaborate me on this

Answer 1

Are you really asking why it uses properties instead of having public fields?

Fields are an implementation detail – they’re how data is stored, which shouldn’t be something the outside world cares about, at least for 99% of types. Properties are part of the contract that a type has in terms of its API – the implementation is up to the type. In other words, it’s a matter of encapsulation. Properties can be expressed in interfaces, as abstract methods etc, precisely because they keep the contract and the implementation separate.

Additionally, properties make databinding, debugging and various other things simpler. I have an article about why properties matter, which you may find useful.

Having said all of this, those properties are implemented in a tedious way – and they don’t obey .NET naming conventions. I would have written them as:

public int UserId { get; set; }
public string UserName { get; set; }
public string Password { get; set; }
// etc