Jump into concepts and practice - no test required
or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Instance Fields and State in C#
📖 Scenario: Imagine you are creating a simple program to keep track of a car's details and its current speed. Each car has its own color and speed, which can change over time.
🎯 Goal: You will build a Car class with instance fields to store the car's color and speed. Then, you will create a car object, update its speed, and display its current state.
📋 What You'll Learn
Create a class called Car with instance fields color and speed
Create an object of the Car class with a specific color
Add a method to update the car's speed
Print the car's color and current speed
💡 Why This Matters
🌍 Real World
Tracking the state of objects like cars, users, or products is common in software. Instance fields store each object's unique data.
💼 Career
Understanding instance fields and object state is fundamental for programming jobs involving object-oriented design and development.
Progress0 / 4 steps
1
Create the Car class with instance fields
Create a class called Car with two instance fields: a string called color and an int called speed. Initialize speed to 0 inside the class.
C Sharp (C#)
Hint
Instance fields are variables inside a class that hold data for each object.
2
Create a Car object with a color
Create a Car object called myCar and set its color field to "Red".
C Sharp (C#)
Hint
Use new Car() to create an object and set the color field directly.
3
Add a method to update the speed
Inside the Car class, add a public method called SetSpeed that takes an int parameter called newSpeed and sets the instance field speed to newSpeed.
C Sharp (C#)
Hint
Methods inside a class can change the instance fields to update the object's state.
4
Update speed and print car details
Use the SetSpeed method on myCar to set the speed to 60. Then, print the car's color and speed in the format: "Car color: Red, Speed: 60".
C Sharp (C#)
Hint
Use the method to update speed and Console.WriteLine with an interpolated string to print.
Practice
(1/5)
1. What is the main purpose of an instance field in a C# class?
easy
A. To store data unique to each object created from the class
B. To define a method that all objects share
C. To create a temporary variable inside a method
D. To hold data shared by all objects of the class
Solution
Step 1: Understand what instance fields represent
Instance fields hold data that belongs to each individual object, not shared across all objects.
Step 2: Differentiate from static fields and methods
Static fields hold shared data, methods define behavior, and local variables are temporary inside methods.
Final Answer:
To store data unique to each object created from the class -> Option A
Quick Check:
Instance field = unique object data [OK]
Hint: Instance fields hold unique data per object, not shared [OK]
Common Mistakes:
Confusing instance fields with static fields
Thinking methods are instance fields
Mixing local variables with instance fields
2. Which of the following is the correct way to declare an instance field named count of type int inside a C# class?
easy
A. static int count;
B. int count() {}
C. void count;
D. int count;
Solution
Step 1: Identify correct syntax for instance field declaration
Instance fields are declared with a type and name, without static keyword or parentheses.
Step 2: Check each option
static int count; is static, not instance. void count; uses void which is invalid for fields. int count() {} looks like a method, not a field.
Final Answer:
int count; -> Option D
Quick Check:
Instance field syntax = type + name [OK]
Hint: Instance fields: type and name, no parentheses or static [OK]
Common Mistakes:
Using static keyword for instance fields
Adding parentheses like a method
Using void as a type for fields
3. What will be the output of this C# code?
class Counter {
private int count = 0;
public void Increment() {
count++;
}
public int GetCount() {
return count;
}
}
var c = new Counter();
c.Increment();
c.Increment();
Console.WriteLine(c.GetCount());
medium
A. 0
B. 2
C. 1
D. Compilation error
Solution
Step 1: Trace the method calls on the object
The object c calls Increment() twice, each increasing count by 1.
Step 2: Check the value returned by GetCount()
After two increments, count is 2, so GetCount() returns 2.
Final Answer:
2 -> Option B
Quick Check:
2 increments = count 2 [OK]
Hint: Each Increment adds 1; two calls mean count is 2 [OK]
Common Mistakes:
Forgetting that count starts at 0
Assuming Increment does not change count
Confusing method return types
4. Identify the error in this C# class that tries to track a score:
class Game {
int score;
public void AddPoints(int points) {
score = score + points;
}
public int GetScore() {
return score;
}
}
var g = new Game();
g.AddPoints(5);
Console.WriteLine(g.GetScore());
medium
A. No error; code runs and prints 5
B. score should be declared static
C. AddPoints method should return int
D. score is not initialized and may have a default value
Solution
Step 1: Check field initialization rules in C#
Instance fields like score default to 0 if not explicitly initialized.
Step 2: Verify method behavior and output
AddPoints adds points correctly, and GetScore returns the updated score. The code prints 5 as expected.
Final Answer:
No error; code runs and prints 5 -> Option A
Quick Check:
Uninitialized int defaults to 0 in C# [OK]
Hint: Instance int fields default to 0 if not set [OK]
Common Mistakes:
Thinking uninitialized int fields cause errors
Believing AddPoints must return a value
Confusing static and instance fields
5. You want to create a class BankAccount that remembers the balance for each account. Which design correctly uses instance fields to track the balance and safely update it?
class BankAccount {
private decimal balance;
public BankAccount(decimal initial) {
balance = initial;
}
public void Deposit(decimal amount) {
if (amount > 0) {
balance += amount;
}
}
public bool Withdraw(decimal amount) {
if (amount > 0 && amount <= balance) {
balance -= amount;
return true;
}
return false;
}
public decimal GetBalance() {
return balance;
}
}
hard
A. Incorrect: Deposit and Withdraw should be static methods
B. Incorrect: balance should be static to share across accounts
C. Correct design: instance field stores balance, methods update and read it safely
D. Incorrect: balance should be public to allow direct access
Solution
Step 1: Check if balance is instance field and encapsulated
Balance is private instance field, unique per object, which is correct for tracking each account.
Step 2: Verify methods safely update and provide access
Deposit and Withdraw check amounts before changing balance, and GetBalance returns current balance safely.
Final Answer:
Correct design: instance field stores balance, methods update and read it safely -> Option C
Quick Check:
Instance field + safe methods = correct state management [OK]
Hint: Use private instance fields with methods to control access [OK]
Common Mistakes:
Making balance static, sharing state wrongly
Using static methods that can't access instance fields