Auto-implemented properties in C Sharp (C#) - Step-by-Step Execution

Concept Flow - Auto-implemented properties

Define class with auto-property

↓

Compiler creates hidden field

↓

Get or set property value

↓

Use property in code

↓

Property returns or updates hidden field

Auto-implemented properties let you quickly create properties without writing explicit backing fields. The compiler handles the hidden storage.

Execution Sample

C Sharp (C#)

public class Person {
  public string Name { get; set; }
}

Person p = new Person();
p.Name = "Alice";
Console.WriteLine(p.Name);

This code creates a Person with an auto-property Name, sets it to "Alice", then prints it.

Execution Table

Step	Action	Property 'Name' Value	Hidden Field Value	Output
1	Create Person object p	null	null
2	Set p.Name = "Alice"	"Alice"	"Alice"
3	Read p.Name	"Alice"	"Alice"	"Alice" printed
4	End of program	"Alice"	"Alice"	Program ends

💡 Program ends after printing the property value.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
p.Name	null	null	"Alice"	"Alice"	"Alice"
Hidden field backing Name	null	null	"Alice"	"Alice"	"Alice"

Key Moments - 3 Insights

Why don't we see a field declared for 'Name' in the code?

Because the compiler automatically creates a hidden field to store the value, as shown by the 'Hidden Field Value' column in the execution_table.

What happens when we set p.Name = "Alice"?

The set accessor stores "Alice" in the hidden field, updating both 'Property Name Value' and 'Hidden Field Value' in the execution_table at step 2.

How does reading p.Name return the correct value?

The get accessor returns the value stored in the hidden field, which is "Alice" at step 3 in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of the hidden field after step 2?

A null

B "Alice"

C "Bob"

D Empty string

💡 Hint

Check the 'Hidden Field Value' column at step 2 in the execution_table.

At which step does the property 'Name' get assigned a value?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the 'Action' column in the execution_table to find when p.Name is set.

If we never set p.Name, what would be the output when reading it?

A Empty string

B "Alice"

C null

D Compilation error

💡 Hint

Refer to the 'Property Name Value' at step 1 before any assignment in the variable_tracker.

Concept Snapshot

Auto-implemented properties:
- Syntax: public Type PropertyName { get; set; }
- Compiler creates hidden field automatically
- Simplifies property declaration
- Get returns hidden field value
- Set updates hidden field value

Full Transcript

Auto-implemented properties in C# let you create properties without writing a backing field. The compiler makes a hidden field behind the scenes. When you set the property, it stores the value in this hidden field. When you get the property, it returns the value from the hidden field. In the example, we create a Person class with a Name property. We set p.Name to "Alice" and then print it. The execution table shows the hidden field storing "Alice" after the set operation. This makes code shorter and easier to read while keeping full property functionality.

Practice

1. What is the main advantage of using auto-implemented properties in C#?

easy

A. They replace constructors for initializing objects.

B. They allow methods to be called without creating an object.

C. They automatically create a private backing field without extra code.

D. They enable multiple inheritance in classes.

Solution

1. Step 1: Understand what auto-implemented properties do

   Auto-implemented properties create a hidden private field automatically to store data without writing extra code.

2. Step 2: Compare with other options

   Options A, B, and C describe unrelated features: constructors, method calls, and inheritance, which are not related to auto-implemented properties.

3. Final Answer:

   They automatically create a private backing field without extra code. -> Option C

4. Quick Check:

   Auto-implemented properties = hidden backing field [OK]

Hint: Auto-properties hide the field; no manual variable needed [OK]

Common Mistakes:

• Confusing properties with methods
• Thinking auto-properties replace constructors
• Believing they enable inheritance

2. Which of the following is the correct syntax for an auto-implemented property named Age of type int?

easy

A. public int Age { get; set; }

B. public int Age() { get; set; }

C. public int Age { get get; set; }

D. public int Age get; set;

Solution

1. Step 1: Identify correct property syntax

   The correct syntax for an auto-implemented property uses curly braces with get; and set; inside: public int Age { get; set; }.

2. Step 2: Check other options for syntax errors

   public int Age() { get; set; } uses parentheses which are for methods, not properties. public int Age { get get; set; } repeats get incorrectly. public int Age get; set; misses braces and semicolons are misplaced.

3. Final Answer:

   public int Age { get; set; } -> Option A

4. Quick Check:

   Property syntax = { get; set; } [OK]

Hint: Properties use braces { } with get; and set; inside [OK]

Common Mistakes:

• Using parentheses instead of braces
• Writing get or set twice
• Omitting braces or semicolons

3. What will be the output of this C# code?

class Person {
    public string Name { get; set; }
}

var p = new Person();
p.Name = "Alice";
Console.WriteLine(p.Name);

medium

A. null

B. Alice

C. Name

D. Compilation error

Solution

1. Step 1: Understand property assignment

   The property Name is auto-implemented, so it stores the value "Alice" when assigned.

2. Step 2: Output the property value

   When Console.WriteLine(p.Name); runs, it prints the stored string "Alice".

3. Final Answer:

   Alice -> Option B

4. Quick Check:

   Property stores "Alice" = output "Alice" [OK]

Hint: Auto-properties store and return assigned values [OK]

Common Mistakes:

• Expecting property name instead of value
• Thinking default null prints as text
• Assuming syntax error without reason

4. Identify the error in this code snippet:

class Car {
    public int Speed { get; private set; }
}

var c = new Car();
c.Speed = 100;
Console.WriteLine(c.Speed);

medium

A. No error; code runs and prints 100.

B. Missing semicolon after property declaration.

C. Property 'Speed' must be static.

D. Cannot assign to 'Speed' because the setter is private.

Solution

1. Step 1: Analyze property access modifiers

   The property Speed has a private setter, so it cannot be assigned outside the class.

2. Step 2: Check assignment in main code

   The line c.Speed = 100; tries to assign from outside, causing a compile error.

3. Final Answer:

   Cannot assign to 'Speed' because the setter is private. -> Option D

4. Quick Check:

   Private setter blocks external assignment [OK]

Hint: Private set means only class can assign property [OK]

Common Mistakes:

• Ignoring setter access level
• Assuming public setter by default
• Confusing property with field

5. You want to create a class Book with an auto-implemented property Title that can be read publicly but only set privately within the class. Which code snippet correctly implements this?

hard

A. public class Book { public string Title { get; private set; } }

B. public class Book { private string Title { get; set; } }

C. public class Book { public string Title { private get; set; } }

D. public class Book { public string Title { get; set; private } }

Solution

1. Step 1: Understand access modifiers for properties

   To allow public reading but private setting, the getter must be public and setter private: get; private set;.

2. Step 2: Check each option's syntax and access

   public class Book { public string Title { get; private set; } } correctly uses public string Title { get; private set; }. public class Book { private string Title { get; set; } } makes the whole property private. public class Book { public string Title { private get; set; } } incorrectly places private before get. public class Book { public string Title { get; set; private } } has invalid syntax.

3. Final Answer:

   public class Book { public string Title { get; private set; } } -> Option A

4. Quick Check:

   Public get + private set = public class Book { public string Title { get; private set; } } [OK]

Hint: Use 'get; private set;' for public read, private write [OK]

Common Mistakes:

• Placing private before get instead of set
• Making whole property private
• Incorrect syntax order for accessors