Why methods are needed in C Sharp (C#) - Visual Breakdown

Concept Flow - Why methods are needed

Start Program

↓

Write code directly

↓

Code repeats tasks

↓

Hard to fix or change

↓

Use methods to group tasks

↓

Call methods when needed

↓

Code is shorter, easier to fix

↓

End Program

This flow shows how writing code directly can cause repetition and difficulty, but using methods groups tasks for easier reuse and maintenance.

Execution Sample

C Sharp (C#)

using System;
class Program {
  static void SayHello() {
    Console.WriteLine("Hello!");
  }
  static void Main() {
    SayHello();
    SayHello();
  }
}

This code defines a method SayHello and calls it twice to print "Hello!" two times.

Execution Table

Step	Action	Method Called	Output	Notes
1	Program starts	No		Main method begins execution
2	Call SayHello()	Yes	Hello!	First call prints Hello!
3	Return from SayHello()	No		Back to Main
4	Call SayHello() again	Yes	Hello!	Second call prints Hello!
5	Return from SayHello()	No		Back to Main
6	Main ends	No		Program finishes

💡 Program ends after Main method finishes

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
No variables used	-	-	-	-

Key Moments - 2 Insights

Why do we call SayHello() twice instead of writing Console.WriteLine("Hello!") twice?

Calling SayHello() reuses the same code, so if we want to change the message, we only update it once inside the method (see execution_table steps 2 and 4).

What happens if we change the message inside SayHello()?

All calls to SayHello() will print the new message, making it easier to fix or update (refer to execution_table steps 2 and 4).

Visual Quiz - 3 Questions

Look at the execution table, what is printed when SayHello() is called the first time?

A "Hello!"

B "Hi!"

C Nothing

D Error

💡 Hint

Check execution_table row 2 under Output column

At which step does the program finish running?

A Step 4

B Step 6

C Step 2

D Step 3

💡 Hint

Look at execution_table last row Step 6 notes

If we wrote Console.WriteLine("Hello!") twice instead of using SayHello(), what would be a problem?

A It would print different messages

B Program would run faster

C Code would be longer and harder to update

D It would cause an error

💡 Hint

Refer to key_moments about code reuse and fixing

Concept Snapshot

Methods group code into reusable blocks.
Call methods to run the grouped code.
Avoid repeating same code multiple times.
Change code in one place inside method.
Makes program shorter and easier to fix.

Full Transcript

This example shows why methods are needed. Without methods, repeating the same code makes programs longer and harder to fix. Here, the method SayHello prints "Hello!". The Main method calls SayHello twice, so the message prints two times. If we want to change the message, we only update SayHello once. This saves time and avoids mistakes. The execution table shows each step: program starts, calls SayHello, prints message, returns, calls again, prints again, then ends. Using methods helps keep code clean and easy to manage.

Practice

1. Why do programmers use methods in C# programs?

easy

A. To organize code into small, clear parts for better understanding

B. To make the program run faster by skipping code

C. To write code only once and never use it again

D. To make the program use more memory

Solution

1. Step 1: Understand the purpose of methods

   Methods help break down code into smaller, manageable pieces.

2. Step 2: Identify the correct reason

   Organizing code into small parts makes it easier to read and maintain.

3. Final Answer:

   To organize code into small, clear parts for better understanding -> Option A

4. Quick Check:

   Methods organize code = A [OK]

Hint: Methods break code into parts for clarity [OK]

Common Mistakes:

• Thinking methods speed up the program directly
• Believing methods increase memory use
• Assuming methods are for one-time code only

2. Which of the following is the correct way to define a method named Greet that returns nothing and takes no parameters in C#?

easy

A. def Greet() { Console.WriteLine("Hello"); }

B. void Greet() { Console.WriteLine("Hello"); }

C. function Greet() { Console.WriteLine("Hello"); }

D. Greet() => Console.WriteLine("Hello");

Solution

1. Step 1: Recall C# method syntax

   In C#, methods use the return type, name, parentheses, and braces.

2. Step 2: Match syntax with options

   void Greet() { Console.WriteLine("Hello"); } uses void return type and correct braces, matching C# syntax.

3. Final Answer:

   void Greet() { Console.WriteLine("Hello"); } -> Option B

4. Quick Check:

   C# method syntax = C [OK]

Hint: C# methods start with return type and name [OK]

Common Mistakes:

• Using 'function' keyword (JavaScript style)
• Using 'def' keyword (Python style)
• Using arrow syntax without proper context

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

void PrintMessage() {
    Console.WriteLine("Hello World");
}

PrintMessage();

medium

A. Syntax error

B. PrintMessage

C. No output

D. Hello World

Solution

1. Step 1: Understand method definition and call

   The method PrintMessage prints "Hello World" when called.

2. Step 2: Check the method call

   The method is called correctly with PrintMessage();, so it runs and prints the message.

3. Final Answer:

   Hello World -> Option D

4. Quick Check:

   Method call prints message = D [OK]

Hint: Method call runs code inside method [OK]

Common Mistakes:

• Thinking method name prints instead of output
• Assuming no output without return
• Confusing syntax error with correct code

4. Identify the error in this C# method and how to fix it:

void ShowNumber()
{
    Console.WriteLine(number);
}

int number = 5;
ShowNumber();

medium

A. The variable 'number' is used before declaration; move declaration above method

B. Method must return int instead of void

C. Missing semicolon after method call

D. Method name should be lowercase

Solution

1. Step 1: Check variable scope

   The variable 'number' is declared after the method, so it's not visible inside the method.

2. Step 2: Fix variable scope

   Move the declaration of 'number' before the method or pass it as a parameter.

3. Final Answer:

   The variable 'number' is used before declaration; move declaration above method -> Option A

4. Quick Check:

   Variable scope error = B [OK]

Hint: Variables must be declared before use in methods [OK]

Common Mistakes:

• Thinking method return type causes error
• Missing semicolon is not the issue here
• Ignoring case sensitivity of method names

5. You want to reuse code that calculates the area of a rectangle multiple times with different sizes. How should you use methods in C# to do this efficiently?

hard

A. Write a method that prints the area directly without parameters

B. Copy and paste the area calculation code everywhere you need it

C. Write a method that takes width and height as parameters and returns the area

D. Use a global variable to store area and update it each time

Solution

1. Step 1: Identify the need for reusable code

   Calculating area multiple times means code should be reusable with different inputs.

2. Step 2: Use method with parameters and return value

   A method that takes width and height and returns area allows reuse without copying code.

3. Final Answer:

   Write a method that takes width and height as parameters and returns the area -> Option C

4. Quick Check:

   Reusable method with parameters = A [OK]

Hint: Use parameters and return to reuse code easily [OK]

Common Mistakes:

• Copy-pasting code instead of using methods
• Printing inside method limits reuse
• Using global variables causes confusion