data encapsulation without properties?

i read a lot about data encapsulation, using properties etc... I tried to do data encapsulation without properties like this and this works:

My question is: why should i use properties? What are the advantages of properties compared to my code? Is this good pratice?

Thanks.

using System;
public class Version1
{
private int x;
public int GetX()
{
return x;
}

public void SetX(int x)
{
if (x > 0)
this.x = x;
else
Console.WriteLine("Must be >0");
}
}

class See
{
public static void Main()
{
Version1 e = new Version1();
e.SetX(10);
Console.WriteLine(e.GetX());
e.SetX(-50);
}
}

A programmer always tries to write 10 lines of code into 2 lines.

What you have written is exact equivalent of a getter and setter.

The shothand way of getter and setter is property.

so yes, your code is correct and does exactly the samething what getter and setter does.

public class Foo
{
private string bar;
public string Bar
{
get { return bar; }
set { bar = value; }
}
}

is equivalent to

public class Foo
{
public string Bar { get; set; }
}

in your case you want to manipulate data based on condition so getter setter is more suitable

public class Foo
{
private int _x;
public int x
{
get { return _x; }
set { x= value; }
}
private string _errorMessage;
public string errorMessage
{
get {
if(x>0){_errorMessage="";
return _errorMessage;
}else
{
return "Can'be less than or equals to zero";
}
}
}
}

as you can see i have a get only property (error message) that is setting internally based on value of x.

so for Business logic validations we often use getter and setter instead of creating a whole new validation method.

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Sachin Singh4y ago
Accepted answer
A programmer always tries to write 10 lines of code into 2 lines.
What you have written is exact equivalent of a getter and setter.
The shothand way of getter and setter is property.

so yes, your code is correct and does exactly the samething what getter and setter does.
public class Foo
{
    private string bar;

    public string Bar
    {
        get { return bar; }
        set { bar = value; }
    }
}
is equivalent to
public class Foo
{
    public string Bar { get; set; }
}
in your case you want to manipulate data based on condition so getter setter is more suitable
public class Foo
{
    private int _x;
   public int x
    {
        get { return _x; }
        set { x= value; }
    }
    private string _errorMessage;

   public string errorMessage
    {
        get {
if(x>0){_errorMessage="";
return _errorMessage;
}else
{
return "Can'be less than or equals to zero";
}
}

    }
}
as you can see i have a get only property (error message) that is setting internally based on value of x.
so for Business logic validations we often use getter and setter instead of creating a whole new validation method.
Valerie Meunier4y ago
Thanks