C# Version HisotryC# Language FeaturesInstalling Visual StudioC# Basic Project StructureHello Wolrd, first C# program
Variables in C# Explicitly typed variables in C#Implicitly typed variables in C#Constants in C#Data types in C#Integral data types in C#Floating-point data types in C#Comparison between Float, Double and DecimalChar data type in C#String data type in C#Boolean data type in C#DateTime data type in C#Enumeration data type in C#Array data type in C#Object data type in C#Dynamic data type in C#Anonymous data type in C#Nullable data type in C#Type casting in C#Type safety in C#Literals in C#Operators in C#Ternary Operator in C#Null coalescing Operator in C#Tilde(~) Operator in C#Keywords in C#Namespace in C#Nullable Types in C#Nullable Helper Class in C#Characteristics of Nullable typesC# Difference between "int" and "int?"
Block statement in C#Empty statement in C#Jump statements in C#Break statement in C#Continue statement in C#Difference between continue and breakGoto statement in C#Return statement in C#Throw statement in C#Yield keyword in C#Checked statement in C#Unchecked statement in C#Lock statement in C#Using statement in C#Enum/Enumeration in C#If-Else statement in C#Switch statement in C#What is a loop in C#?For loop in C#While loop in C#Do while loop in C#Foreach loop in C#Nested loop in C#Infinite loop in C#
C# Method or FunctionC# Method Parameters and ArgumentsC# Method OverloadingC# Return StatementsC# Static vs. Instance MethodsC# Method ModifiersC# Method Signatures and Naming ConventionsC# Function Documentation and CommentsC# Value Type ParametersC# Ref Type ParametersDifference between Value and Ref TypeC# Out ParametersDifference between Ref and out parametersC# Optional parametersAre Nullable types reference types in C#"
Exception Handling in C#Types of exception in C#Try catch finally in C#finally block in C#try block without catch blockMultiple catch blocks in exceptionCatch multiple exceptions in C#Base class of exception in C#finally block execution in C#finally block execution in case of errorFinally and return statementWays to use try-catch-finallyException throw from finally block"throw" and "throw ex" in C#Differene between finalize() and finallyInner exception in C#Error types in C#Catch multi exception by single catch blockUser defined/custom excetion in C#Compile and run time exception in C#Difference between "error" and "exception"System and application exception in C#Exception handling abuse in c#?
C# String BasicsC# String ManipulationC# String FormattingC# String Comparison and SearchingC# StringBuilder ClassC# Regular ExpressionsC# Unicode and EncodingC# String Parsing and ConversionDifference between "string" and "String"C# String Escape SequenceC# Mutable and Immutable ConceptProve that string is immutableString value stored in memoryDifference between string and stringbuilderOverride the tostring() method
Enum/enumeration in C#Can you inherit enum in C#?Convert enum to stringConvert enum to list in C#Cast int value to enum in C#Get int value from enum in C#Convert string to enum in C#Usage of enum in switch case statementLoop through all enum valuesUse tilde(~) with Enum
Main() method basics in C#More than one "Main()" method in C#Static Main() method in C#Overload Main() method in C#Override Main() method in C#Access modifiers of Main() method in C#Non-static method in C#Main() method arguments and return typeasync Main() method in C#Class without Main() method in C#Main() method rules in C#
Recursion in C#Base condition in recursion in C#Recursive Algorithms in C#Tree traversal using recursion in C#Stack overflow error in recursionBack tracking using recursionIndirect recursion in C#Recursive data structures in C#Tail Recursion in C#Recursive problem solvingRecursion vs Iteration
C# File and File InfoC# StreamReader and StreamWriterC# FileStream and BinaryReader/BinaryWriterC# Directory and DirectoryInfo ClassesC# File PathsC# File and Directory OperationsC# File Exceptions and Error HandlingC# File Serialization and DeserializationC# File System Watcher
What is array?Single dimension arrayMulti dimension arrayJagged arrayParam arrayArray with multi data typesDifferent data types from object arrayArray with non-default valuesArray methods and propertiesArray manipulation techniquesArray sorting algorithmsArray Searching algorithms(linear, binary search)Array finding maximum and minimumArray of Reference Types
C# GenericsC# Generic Constraints
C# ArrayListC# Array vs ArrayListC# ListC# SortedListC# DictionaryC# HashtableC# Dictionary vs HashtableC# HashSetC# Hashtable vs HashSetC# StackC# Queue
C# IEnumerableC# IEnumeratorC# ICollectionC# IListC# IDictionaryC# IDisposableC# IComparableC# IEquatableC# ICloneableC# IQueryableC# INotifyPropertyChangedC# INotifyCollectionChangedC# IFormattableC# IAsyncResultC# IComparerC# IEqualityComparerC# IHttpHandlerC# IHttpModule
C# DelegatesC# Single-Cast DelegateC# Multi-Cast DelegateC# Generic DelegatesC# Func DelegateC# Action DelegateC# Predicate DelegateC# Anonymous MethodsC# EventsDifference Between Event & DelegateDifference Between Interface & DelegateC# Covariance and Contravariance
Previous
Next

C# - using statement

In C#, the "using" statement has two significant applications: firstly, as a "directive" to simplify code by referencing namespaces, and secondly, as a statement for automatically managing memory allocation and resource disposal.

1. Understanding the Using Directive in C#

The "using directive" in C# serves a different purpose compared to the "using statement." It's used to include namespaces in a C# program, making the types defined in those namespaces available without needing to fully qualify their names each time. Let's break this down with an example:

Overview:
  • Purpose: It simplifies code by allowing you to use just the class name instead of the full namespace-qualified name. For example, instead of writing System.Console.WriteLine, you can write Console.WriteLine if you have using System; at the top of your file.
  • Namespaces: A namespace is a collection of classes, interfaces, structs, enums, and delegates. Common namespaces in C# include System, System.Collections.Generic, and System.Linq.
  • Avoiding Name Collisions: The using directive also helps to avoid name collisions by specifying which namespaces are in use.
Scenario: Creating a console application

Creating a console application that prints a message, using System namespace.


using System;

class Program
{
    static void Main()
    {
        Console.WriteLine("Hello, World!");
    }
}
Explanation:
  • using System; allows the program to use classes in the System namespace.
  • Console.WriteLine is a method in the System namespace. Thanks to the using directive, you don't need to write System.Console.WriteLine.
Output:

When this program is run, it will output:


Hello, World!
Conclusion:

The using directive in C# makes code cleaner and more readable by allowing the use of short names for types from different namespaces. It's a fundamental part of C# programming, helping to organize code and manage namespaces efficiently.

2. Understanding the using Statement to release memory allocation

The "using statement" in C# is a powerful feature that simplifies the management of resources, particularly those that require proper disposal like file handles or database connections. Here's a straightforward explanation with an example:

  • Purpose: The using statement ensures that resources are properly disposed of once they are no longer needed. It's a syntactic sugar for a try/finally block.
  • How It Works: When the block of code under using is finished, the Dispose method is automatically called on the object, ensuring resources are freed up efficiently.
  • Common Uses: It's frequently used with classes that implement the IDisposable interface, like file streams, database connections, etc.
Scenario: Example with File Handling

Suppose you want to read text from a file and then automatically close the file handle when done.

Here's a simple C# program using the using statement for reading from a file:


using System;
using System.IO;

class Program
{
    static void Main()
    {
        string filePath = "example.txt"; // Assume this file exists with some content

        using (StreamReader reader = new StreamReader(filePath))
        {
            string content = reader.ReadToEnd();
            Console.WriteLine("File content:");
            Console.WriteLine(content);
        }

        // At this point, the StreamReader is automatically disposed.
    }
}
Explanation:
  • StreamReader reader = new StreamReader(filePath) initializes a new StreamReader for the file.
  • The using block ensures that reader.Dispose() is called automatically at the end of the block, closing the file and freeing resources.
  • reader.ReadToEnd() reads all text from the file.
Output:

The output will depend on the contents of "example.txt". For example, if "example.txt" contains "Hello, World!", the output will be:


	File content:
	Hello, World!

After the using block is executed, the StreamReader is automatically disposed of, ensuring that the file is closed properly without the need for explicit code to handle this task.

Conclusion:

The using statement in C# is an elegant way to handle resources, particularly for those that need explicit disposal. It simplifies code and helps prevent resource leaks by automatically disposing of resources.

Previous
Next