Using statement with file streams in C Sharp (C#) - Step-by-Step Execution

Concept Flow - Using statement with file streams

Start

↓

Open file stream

↓

Execute code block

↓

Dispose file stream automatically

↓

End

The using statement opens a file stream, runs code inside its block, then automatically closes the stream when done.

Execution Sample

C Sharp (C#)

using (var fs = new FileStream("test.txt", FileMode.OpenOrCreate))
{
    byte[] data = new byte[] {1, 2, 3};
    fs.Write(data, 0, data.Length);
}

This code opens or creates 'test.txt', writes bytes 1,2,3, then closes the file automatically.

Execution Table

Step	Action	FileStream State	Output/Effect
1	Enter using block, open file stream 'test.txt'	Open	File 'test.txt' ready for writing
2	Create byte array data = {1,2,3}	Open	Data prepared in memory
3	Write data to file stream	Open	Bytes 1,2,3 written to file
4	Exit using block	Disposed	File stream closed automatically
5	End of program	Disposed	File safely closed, no resource leak

💡 Using block ends, file stream disposed automatically to free resources

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
fs	null	Open file stream	Open file stream with data written	Disposed (closed)
data	null	byte[] {1,2,3}	byte[] {1,2,3}	byte[] {1,2,3}

Key Moments - 3 Insights

Why does the file stream close automatically after the using block?

Because the using statement calls Dispose() on the file stream at the end of the block, as shown in step 4 of the execution_table.

Can we use the file stream outside the using block?

No, the file stream is disposed and closed after the using block ends, so it cannot be used beyond step 4.

What happens if an exception occurs inside the using block?

The using statement still ensures Dispose() is called, so the file stream closes safely even if an error happens.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'fs' after step 3?

A Disposed (closed)

B Open file stream with data written

C Null

D Not created yet

💡 Hint

Check the 'FileStream State' column at step 3 in execution_table

At which step does the file stream get closed automatically?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look for 'Disposed' state in the 'FileStream State' column in execution_table

If we remove the using statement, what risk do we face?

A File stream closes automatically anyway

B The program will not compile

C File stream might not close, causing resource leaks

D The file will be deleted

💡 Hint

Recall that using ensures Dispose() is called automatically as shown in key_moments

Concept Snapshot

using statement syntax:
using (var resource = new Resource()) {
  // use resource
}

Behavior:
- Opens resource
- Runs code block
- Automatically calls Dispose() to close resource

Key rule: Always use using with file streams to avoid resource leaks.

Full Transcript

The using statement in C# helps manage file streams safely. It opens the file stream at the start of the block, lets you run code to read or write files, then automatically closes the stream when done. This prevents forgetting to close files and leaking resources. In the example, a file stream opens 'test.txt', writes bytes 1, 2, 3, then closes automatically at the end of the using block. Even if an error happens, the file stream will close safely. This is shown step-by-step in the execution table and variable tracker. Remember, the file stream is only valid inside the using block and is disposed right after.

Practice

1. What is the main purpose of using the using statement with file streams in C#?

easy

A. To automatically close and dispose the file stream after use

B. To open multiple files at the same time

C. To read the file contents faster

D. To prevent the file from being edited

Solution

1. Step 1: Understand the role of using with resources

   The using statement ensures that the resource it wraps, like a file stream, is properly closed and disposed after the block finishes.

2. Step 2: Apply this to file streams

   File streams hold system resources that must be released to avoid file locks or memory leaks. using handles this automatically.

3. Final Answer:

   To automatically close and dispose the file stream after use -> Option A

4. Quick Check:

   Using = automatic resource cleanup [OK]

Hint: Using auto-closes files to avoid manual cleanup [OK]

Common Mistakes:

• Thinking using speeds up file reading
• Believing using prevents file editing
• Assuming using opens multiple files simultaneously

2. Which of the following is the correct syntax to open a file for reading using a using statement in C#?

easy

A. using FileStream fs = new FileStream("file.txt", FileMode.Open);

B. using var fs = FileStream("file.txt", FileMode.Open);

C. using (var fs = new FileStream("file.txt", FileMode.Open)) { }

D. using (FileStream fs = FileStream.Open("file.txt")) { }

Solution

1. Step 1: Recognize correct using block syntax

   The using statement requires parentheses around the resource declaration and a block of code inside braces.

2. Step 2: Check each option

   using (var fs = new FileStream("file.txt", FileMode.Open)) { } uses using (var fs = new FileStream(...)) { } which is correct. using var fs = FileStream("file.txt", FileMode.Open); misses parentheses. using FileStream fs = new FileStream("file.txt", FileMode.Open); misses braces. using (FileStream fs = FileStream.Open("file.txt")) { } uses a non-existent method FileStream.Open.

3. Final Answer:

   using (var fs = new FileStream("file.txt", FileMode.Open)) { } -> Option C

4. Quick Check:

   Using needs parentheses and braces [OK]

Hint: Using needs parentheses and braces for resource block [OK]

Common Mistakes:

• Omitting parentheses around resource declaration
• Forgetting braces after using statement
• Calling non-existent FileStream methods

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

using System;
using System.IO;

class Program {
    static void Main() {
        using (var fs = new FileStream("test.txt", FileMode.Create)) {
            byte[] data = {72, 105};
            fs.Write(data, 0, data.Length);
        }
        using (var fs = new FileStream("test.txt", FileMode.Open)) {
            byte[] buffer = new byte[2];
            fs.Read(buffer, 0, buffer.Length);
            Console.WriteLine(System.Text.Encoding.ASCII.GetString(buffer));
        }
    }
}

medium

A. Error: File not found

B. 72,105

C. System.Byte[]

D. Hi

Solution

1. Step 1: Write bytes to file

   The code writes bytes 72 and 105 to "test.txt". These bytes represent ASCII characters 'H' and 'i'.

2. Step 2: Read bytes and convert to string

   The code reads the two bytes back and converts them to a string using ASCII encoding, resulting in "Hi".

3. Final Answer:

   Hi -> Option D

4. Quick Check:

   Bytes 72,105 = 'Hi' string [OK]

Hint: ASCII codes 72 and 105 spell 'Hi' [OK]

Common Mistakes:

• Expecting byte array printed instead of string
• Confusing byte values with characters
• Assuming file read fails without checking creation

4. Identify the error in the following code snippet that uses a using statement with a file stream:

using (FileStream fs = new FileStream("data.txt", FileMode.Open))
    byte[] buffer = new byte[100];
    fs.Read(buffer, 0, buffer.Length);

medium

A. FileMode.Open is invalid for reading

B. Missing braces {} after the using statement

C. Buffer size should be 0

D. FileStream cannot be used with using

Solution

1. Step 1: Check using statement syntax

   The using statement requires braces {} to define the scope of the resource usage.

2. Step 2: Analyze the code block

   Without braces, only the first line after using is considered inside the block. The buffer declaration and read call are outside, causing a compile error.

3. Final Answer:

   Missing braces {} after the using statement -> Option B

4. Quick Check:

   Using needs braces for multiple statements [OK]

Hint: Always use braces {} after using for multiple lines [OK]

Common Mistakes:

• Omitting braces for multiple statements
• Confusing FileMode.Open with invalid mode
• Thinking buffer size must be zero

5. You want to read all lines from a text file and count how many lines contain the word "error" using a using statement with a StreamReader. Which code snippet correctly implements this?

hard

A. int count = 0;
using (var reader = new StreamReader("log.txt")) {
string line;
while ((line = reader.ReadLine()) != null) {
if (line.Contains("error")) count++;
}
}
Console.WriteLine(count);

B. int count = 0;
using var reader = new StreamReader("log.txt");
while (reader.ReadLine() != null) {
if (reader.ReadLine().Contains("error")) count++;
}
Console.WriteLine(count);

C. int count = 0;
using (StreamReader reader = new StreamReader("log.txt")) {
foreach (var line in reader) {
if (line.Contains("error")) count++;
}
}
Console.WriteLine(count);

D. int count = 0;
using (var reader = new StreamReader("log.txt")) {
string line = reader.ReadToEnd();
if (line.Contains("error")) count++;
}
Console.WriteLine(count);

Solution

1. Step 1: Understand reading lines with StreamReader

   The correct way to read lines one by one is using ReadLine() inside a loop until it returns null.

2. Step 2: Check each option's logic

   int count = 0; using (var reader = new StreamReader("log.txt")) { string line; while ((line = reader.ReadLine()) != null) { if (line.Contains("error")) count++; } } Console.WriteLine(count); reads each line once and checks for "error" correctly. int count = 0; using var reader = new StreamReader("log.txt"); while (reader.ReadLine() != null) { if (reader.ReadLine().Contains("error")) count++; } Console.WriteLine(count); calls ReadLine() twice per loop, skipping lines. int count = 0; using (StreamReader reader = new StreamReader("log.txt")) { foreach (var line in reader) { if (line.Contains("error")) count++; } } Console.WriteLine(count); tries to foreach over StreamReader which is invalid. int count = 0; using (var reader = new StreamReader("log.txt")) { string line = reader.ReadToEnd(); if (line.Contains("error")) count++; } Console.WriteLine(count); reads entire file as one string and counts only once.

3. Final Answer:

   Option A correctly reads lines and counts occurrences -> Option A

4. Quick Check:

   ReadLine loop + check line contains [OK]

Hint: Use while ((line = ReadLine()) != null) to read lines [OK]

Common Mistakes:

• Calling ReadLine() twice per loop skipping lines
• Trying to foreach over StreamReader directly
• Using ReadToEnd() and counting only once