Why file operations matter in C Sharp (C#) - Performance Analysis

Time Complexity: Why file operations matter

O(n)

Understanding Time Complexity

When working with files, the time it takes to read or write data can change a lot depending on how much data there is.

We want to understand how the time needed grows as the file size grows.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

using System.IO;

void WriteNumbersToFile(string path, int n)
{
    using StreamWriter writer = new StreamWriter(path);
    for (int i = 0; i < n; i++)
    {
        writer.WriteLine(i);
    }
}
    

This code writes numbers from 0 up to n-1 into a file, one number per line.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Writing a line to the file inside a loop.
• How many times: The loop runs n times, so the write happens n times.

How Execution Grows With Input

As the number n grows, the number of write operations grows the same way.

Input Size (n)	Approx. Operations
10	10 writes
100	100 writes
1000	1000 writes

Pattern observation: The time grows directly with the number of lines written.

Final Time Complexity

Time Complexity: O(n)

This means the time to write grows in a straight line with the number of lines you write.

Common Mistake

[X] Wrong: "Writing to a file is always instant and does not depend on how much data is written."

[OK] Correct: Writing takes more time as you write more lines because each line is a separate operation that the computer must handle.

Interview Connect

Understanding how file operations scale helps you write programs that handle data efficiently and avoid slowdowns when files get big.

Self-Check

"What if we buffered multiple lines before writing to the file? How would the time complexity change?"

Practice

1. Why are file operations important in C# programs?

easy

A. They help the program use less memory.

B. They make the program run faster.

C. They change the program's user interface.

D. They allow programs to save and retrieve data on the computer.

Solution

1. Step 1: Understand the purpose of file operations

   File operations let programs save data to files and read data back later.

2. Step 2: Connect to program persistence

   This means data can be kept even after the program stops running.

3. Final Answer:

   They allow programs to save and retrieve data on the computer. -> Option D

4. Quick Check:

   File operations = save/load data [OK]

Hint: Remember: files keep data after program ends [OK]

Common Mistakes:

• Thinking file operations speed up the program
• Confusing file operations with UI changes
• Believing file operations reduce memory use

2. Which of the following is the correct way to open a file for writing in C#?

easy

A. File.OpenWrite("data.txt");

B. File.OpenRead("data.txt");

C. File.ReadAllText("data.txt");

D. File.Delete("data.txt");

Solution

1. Step 1: Identify methods for file writing

   File.OpenWrite opens a file stream for writing data.

2. Step 2: Check other options

   File.OpenRead is for reading, ReadAllText reads all text, Delete removes the file.

3. Final Answer:

   File.OpenWrite("data.txt"); -> Option A

4. Quick Check:

   OpenWrite = open file to write [OK]

Hint: OpenWrite means open file to write data [OK]

Common Mistakes:

• Using OpenRead when writing is needed
• Confusing ReadAllText with opening a file stream
• Choosing Delete instead of opening a file

3. What will the following C# code output?

using System;
using System.IO;

class Program {
  static void Main() {
    File.WriteAllText("test.txt", "Hello World");
    string content = File.ReadAllText("test.txt");
    Console.WriteLine(content);
  }
}

medium

A. Hello World

B. Empty line

C. File not found error

D. test.txt

Solution

1. Step 1: Write text to file

   File.WriteAllText creates or overwrites "test.txt" with "Hello World".

2. Step 2: Read text from file and print

   File.ReadAllText reads the content back, which is "Hello World", then prints it.

3. Final Answer:

   Hello World -> Option A

4. Quick Check:

   WriteAllText + ReadAllText = same text output [OK]

Hint: Write then read file outputs saved text [OK]

Common Mistakes:

• Expecting filename instead of file content
• Thinking file is missing causing error
• Assuming output is empty

4. Identify the error in this C# code snippet for reading a file:

string content = File.ReadAllText("missing.txt");
Console.WriteLine(content);

medium

A. The file path is incorrect syntax.

B. Console.WriteLine cannot print strings.

C. File.ReadAllText throws an exception if file is missing.

D. The code is missing a semicolon.

Solution

1. Step 1: Understand File.ReadAllText behavior

   If the file "missing.txt" does not exist, File.ReadAllText throws a FileNotFoundException.

2. Step 2: Check other options

   Syntax is correct, Console.WriteLine can print strings, semicolons are present.

3. Final Answer:

   File.ReadAllText throws an exception if file is missing. -> Option C

4. Quick Check:

   Missing file causes exception in ReadAllText [OK]

Hint: Missing file causes exception on read [OK]

Common Mistakes:

• Assuming missing file returns empty string
• Thinking Console.WriteLine can't print strings
• Believing syntax error due to semicolon

5. You want to save user settings in a file and load them when the program starts. Which approach best ensures data is saved and loaded correctly in C#?

hard

A. Use Console.WriteLine to save settings and Console.ReadLine to load them.

B. Use File.WriteAllText to save settings as JSON and File.ReadAllText to load and parse JSON.

C. Use File.Delete to remove old settings before saving new ones.

D. Use File.OpenRead to save settings and File.OpenWrite to load them.

Solution

1. Step 1: Choose correct methods for saving and loading

   File.WriteAllText saves text data like JSON; File.ReadAllText reads it back for parsing.

2. Step 2: Evaluate other options

   Console methods do not save to files; File.Delete removes files but doesn't save; OpenRead/OpenWrite are for streams, not direct save/load.

3. Final Answer:

   Use File.WriteAllText to save settings as JSON and File.ReadAllText to load and parse JSON. -> Option B

4. Quick Check:

   WriteAllText + ReadAllText for file save/load [OK]

Hint: Save as JSON text, read and parse it back [OK]

Common Mistakes:

• Using Console methods for file storage
• Deleting files unnecessarily before saving
• Mixing up OpenRead and OpenWrite roles