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# - Difference between error and exception

In C#, both errors and exceptions are issues that can disrupt the normal flow of a program, but they are distinct in nature. Let's explore the difference between errors and exceptions with a simple code example:

Understanding the Difference Between Errors and Exceptions in C#

  • Errors: Errors in C# are typically compile-time issues that prevent the program from building or running. These errors occur due to violations of language rules or improper code structure. Errors cannot be caught or handled during runtime; they must be fixed before the program can be executed.
  • Exceptions: Exceptions, on the other hand, are runtime issues that occur when a program is running. These are unexpected conditions or events that can disrupt the normal execution of a program. Exceptions can be caught and handled using try-catch blocks to gracefully recover from errors and continue program execution.

Source Code


using System;

class Program
{
    static void Main()
    {
        // Error: Missing semicolon
        Console.WriteLine("Hello, world!")
        
        // Exception: Division by zero
        int numerator = 10;
        int denominator = 0;
        try
        {
            int result = numerator / denominator; // Division by zero exception
            Console.WriteLine("Result: " + result);
        }
        catch (DivideByZeroException ex)
        {
            Console.WriteLine("Exception caught: " + ex.Message);
        }
    }
}

Explanation

  • In the source code above, there is a deliberate error by missing a semicolon at the end of the line: Console.WriteLine("Hello, world!"). This is a compile-time error and will prevent the program from building.
  • The program also contains an exception scenario where we attempt to divide by zero with the variables numerator and denominator. This is a runtime exception and can be caught and handled using a try-catch block. When an exception occurs, the program flow is disrupted, and the control is transferred to the catch block.

Output


Compilation error: ; expected

Exception caught: Attempted to divide by zero.

In this example:

  • The error (missing semicolon) prevents the program from compiling, and you will receive a compilation error message.
  • The exception (division by zero) occurs during runtime and is caught by the try-catch block. The program displays the exception message and continues execution after the catch block.

Conclusion

Errors are compile-time issues that prevent the program from building, while exceptions are runtime issues that disrupt program execution but can be caught and handled using try-catch blocks. Understanding the difference between these two is crucial for writing robust C# programs.

Points to Remember:
  1. Errors vs. Exceptions:
    • Errors are compile-time issues that prevent the program from building or running. They are usually caused by syntax errors, type mismatches, or code structure violations. Errors must be fixed before the program can be executed.
    • Exceptions are runtime issues that occur during program execution. They are unexpected conditions or events that disrupt the normal flow of the program. Exceptions can be caught and handled to gracefully recover from issues.
  2. Compile-Time vs. Runtime:
    • Errors are detected and reported by the compiler during the compilation phase.
    • Exceptions occur during the runtime of the program when a specific condition is encountered.
  3. Handling Exceptions:
    • Exceptions can be caught and handled using try-catch blocks. This allows you to respond to unexpected situations and continue program execution.
    • The try block contains the code that might throw an exception, while the catch block handles the exception if it occurs.
  4. Common Exception Types:
    • Common exception types in C# include DivideByZeroException, NullReferenceException, ArgumentException, and more. Each exception type represents a specific error condition.
  5. Custom Exceptions:
    • You can create custom exception classes by inheriting from the Exception base class. This allows you to define your own exception types tailored to your application's needs.
  6. Exception Propagation:
    • If an exception is not caught within a method, it propagates up the call stack to higher-level methods. If unhandled, it can terminate the program.
  7. Handling Errors:
    • Errors must be fixed by modifying the code to adhere to language rules and correct coding practices. The compiler provides error messages to guide you in fixing these issues.
  8. Error Prevention:
    • Writing clean, well-structured code helps prevent both errors and exceptions. Proper code reviews and testing are essential to catch issues early.
  9. Logging and Reporting:
    • Logging exception details is crucial for debugging and troubleshooting. It helps identify the root causes of exceptions and aids in improving code reliability.
  10. Graceful Degradation:
    • When handling exceptions, consider graceful degradation strategies. This means ensuring that your program can continue functioning or fail gracefully without crashing.
  11. Documentation:
    • Document your code, including potential exceptions that methods may throw. This helps other developers understand how to use your code and handle exceptions appropriately.
  12. Exception Safety:
    • Ensure that your code is exception-safe. This means that it behaves correctly even in the presence of exceptions and leaves the program in a consistent state.
  13. Testing Scenarios:
    • Test your code under various scenarios, including situations that might lead to exceptions. Unit tests and integration tests can help identify and handle exceptions.
  14. Robust Error Handling:
    • Develop a robust error-handling strategy that considers the types of exceptions your application may encounter and how to respond to them effectively.
  15. Continuous Improvement:
    • Continuously monitor and improve error and exception handling in your codebase. Learn from past issues and enhance error reporting and handling mechanisms.
Previous
Next