Private Variables vs Properties in C# -

this question has answer here:

• why use private members use public properties set them? 5 answers
• why use simple properties instead of fields in c#? [duplicate] 5 answers

i teaching myself c# , curious need declaring private member variables accessed public properties. textbook i'm using says sake of encapsulation, why need private variables begin if properties can changed depending on 'get' or 'set' functions? here's example:

namespace practice {     struct person     {         private int id;         private string name;          public int id { {return id;} set {id = value;} }         public string name { get; set; }         public int age { get; set; }     }     class program     {          static void main(string[] args)         {              person person = new person();             person.id = 548;             person.name = "dude";              console.writeline(person.name);         }     } } 

so name , id operate exact same way, what's purpose of declaring private int id , private string name?

in case, since not doing backing field (private field), don't need it. can work auto properties (but, remember, auto properties use backing field in background).

having backing field useful if doing operation it, example, if want verify id should greater 100, can

public int id {         {         return id;     }     set     {         if(id <= 100) throw new exception("invalid id provided");         id = value;     } } 

if try apply same logic on property, instead of backing field, will/could run infinite recursion.