[C#] Properties question

[MatazaNZ]

Hi all. I'm a tad confused right now. I've been using properties in C# for a while now, and I want to ask very quickly if there is any real difference between this

public string filePath { get; set; }public sting name { get; set; }

And this

private string filePath;private string name;public string FilePath{    get {return filePath;}    set {filePath = value;}}public string Name{    get {return name;}    set {name = value;}}

I am massively confused right now, and I might even be thinking too far into things. I decided if anyone could answer, the LTT community can. I've tried googling it, but most of what I found were just comparisons between methods and properties. I believe both of these types are properties

[madknight3]

No, they are equivalent. Automatic properties are there for convenience.

 

With that said, obviously the properties written out fully can do more.

[cluelessgenius]

well i dont know what its called in english but the ones below are public properties that only reference the private once.

that way you can do stuff as getter or setter. simple formulas fo example or stuff like that

[MatazaNZ]

No, they are equivalent. Automatic properties are there for convenience.

 

With that said, obviously the properties written out fully can do more.

 

 

well i dont know what its called in english but the ones below are public properties that only reference the private once.

that way you can do stuff as getter or setter. simple formulas fo example or stuff like that

So they are basically the same thing at the core, just the second ones are able to implement more to them, such as data validation?

[cluelessgenius]

So they are basically the same thing at the core, just the second ones are able to implement more to them, such as data validation?

yes basicly, i usually use the second once because of that. if you think hard enough almost every propertie has some code to validate it or something. the more you can put in setters and getter the less you have to do somewhere else in the code it saves a lot of code and dokumentation 

[madknight3]

Simply use the automatic property whenever you don't add any more code. If you do, use the long version. When you do use the long version because you're adding in more code, the getter should be kept simple and shouldn't throw exceptions, while the setter can (source).

 

 

Also, if anyone wonders what the difference is between an automatic property and a simple public field

public int foo { get; set; }public int bar;

then see this answer.

[MatazaNZ]

Simply use the automatic property whenever you don't add any more code. If you do, use the long version. When you do use the long version because you're adding in more code, the getter should be kept simple and shouldn't throw exceptions, while the setter can (source).

 

 

Also, if anyone wonders what the difference is between an automatic property and a simple public field

public int foo { get; set; }public int bar;

then see this answer.

so if you're just going to be using basic fields with no need for validation or extra code, it's best to use the automatic properties?

[madknight3]

so if you're just going to be using basic fields with no need for validation or extra code, it's best to use the automatic properties?

Yeah, why write the extra code when you don't need it right?