What is the difference between the => operator and auto property?

Question

What is the difference between the => operator for properties and auto property in C#?

I have properties like

public string Name => name;

but Resharper suggests that I convert them to auto properties instead:

public string Name { get; }

I do not see any added value from this. Is there any difference between the two?

`=>` gets more exciting when the RHS is not a simple field value — , Apr 30 '18 at 14:44
@SebastianHofmann;: if that is true, then the get way is just way clearer. that onle would be the "added value" of writing it like that. — Christopher, Apr 30 '18 at 14:44
@Christopher it's true, if you write the property with `{get {return...}}`, Visual Studio suggests to replace this with an expression body, aka `=>` — Sebastian Hofmann, Apr 30 '18 at 14:47

score 2 · Answer 1 · answered Apr 30 '18 at 14:44

2

The difference is that the auto property creates the backing field automatically. If you don't need it, the auto property is probably more convenient.

answered Apr 30 '18 at 14:44

adjan

13,371
2
31
48

1

An auto-implemented property does create a backing field, but you can't use it in your code, it's not accessible to you. – Zohar Peled Apr 30 '18 at 14:55

What is the difference between the => operator and auto property?

1 Answers1