Why to use properties get set in C#

Question

1.00/5 (1 vote)

See more:

I came across a topic named properties(get,set) to access a private variable of a class outside that class. But if we can set its access to public we can achieve same to use the variable outside that class. Then, why to use property concept any simple explanation and sample code, thanks.

What I have tried:

When I can do this by setting isGirl to public:

C#

class MainClass
    {
        class SubClass
        {
            public static bool isGirl;
          
        }
        static void Main()
        {
            SubClass.isGirl = true;
            Console.WriteLine(SubClass.isGirl);
        }
    }

In contrast, this is a property of the name variable which is quite lengthy. If public and property both do the same thing and also property must be within the same class where the variable is private, then why to use property?

C#

public bool IsGirl
          {
              get { return isGirl; }
              set { isGirl = value; }
          }

Posted 14-May-22 1:42am

Shazma Batool

Updated 14-May-22 7:35am

PIEBALDconsult

v2

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard MacCutchan · Answer 1 · 2022-05-14T02:30:00

Solution 1

In simple cases like the above it is not critical to do it this way. But in more complex classes it may be that some code outside the class could store garbage in the object. Using getters and setters allows you to protect the object and always ensure that it only stores valid data.

Posted 14-May-22 2:30am

Richard MacCutchan

Comments

Maciej Los 14-May-22 14:17pm

5ed!

OriginalGriff · Answer 2 · 2022-05-14T03:17:00

One good reason is that properties are "variables with code" - if you use a public variable then the outside world can access or change the value of the variabel at any point - which means that if you want to make changes to your class you have to consider any possible effects on the outside world before you make them,. or you could break existing code.

For example, if you have a User class, with a public Name variable everything is fine. But in a months time, you need to reference the forenames and surname separately - so you create a FirstName and a Surname variable and delete the Name. And outside code which tries to access the Name fails!

If you used a Property, then when it is set, your code can break teh name up and store it in ForeName and Surname, then your code can assemble the full Name from the two parts on demand.
Existing code doesn't break, and your new requirement has been added.

Another advantage: some Controls can use Properties to display columns - for example, you can set a List<MyClass> as the DataSource for a DataGridView and it will display only the properties in separate columns and none of the fields.

PIEBALDconsult · Answer 3 · 2022-05-14T07:35:00

Fields should very rarely be public, but it may make sense some times.

In the particular case above, I recommend making the setter private:
public bool IsGirl { get ; private set ; }
You can't do that with a field.

Additionally, by using a Property, the setter can include validation or logging when such is desirable.

C#

public bool IsGirl
{
  get { return isGirl; }

  set 
  {
    LOG.Write ( "Changing value of IsGirl" , value ) ;

    isGirl = value;
  }
}

Why to use properties get set in C#

3 solutions

Solution 1

Solution 3

Solution 4

Add your solution here

Preview 0