
Delve into .NET development with C#, covering programming fundamentals, object-oriented principles, exception handling, and multithreading. Gain hands-on experience to build cross-platform applications effectively.

csharp.tar.gz

CSharp-Compile-Run-code

.NET is Microsoft’s free and open source framework for developing native software applications on Linux, macOS, and Windows. The power of cross-platform development allows developers to design, code, and run programs on a wide array of platforms.

This course is an introduction to developing .NET applications using C#. You’ll start start with a comprehensive review of C# and computer programming fundamentals: data types, conditionals, loops, methods, and more. You’ll then review the basics of object-oriented programming before diving into methods, exception handling, delegation, and events. With this foundation, you’ll continue building interfaces, collections, database operations, and multithreading. You’ll wrap up with process improvements using dynamic binding, garbage collection, and unmanaged resources.

By the end of this course, you’ll have hands-on experience with C# and .NET, and be ready to build applications using object-oriented programming principles on almost any platform.

Mastering C# and .NET

## Synchronization using mutex

The word mutex stands for **mutual exclusion**. It’s a special object that can restrict access to a critical section of the code. In essence, there’s nothing much that separates a mutex from the `lock` statement or the `Monitor` class. We create a mutex object and, whenever we enter a critical section, we acquire the lock for the mutex. If the mutex has already been acquired by another thread, then the thread has to wait until the mutex is released.

> **Note:** The mutex in .NET is represented by a class called `Mutex`, which resides in the `System.Threading` namespace.

Unlike the `lock` statement and `Monitor`, `Mutex` doesn’t need a separate locker object because it serves this purpose itself:


```C#
// Mutex
static Mutex mutex = new Mutex();

static void SomeMethod()
{
    // Critical section begins here
    mutex.WaitOne();
    try
    {
        // Critical section code
    }
    finally
    {
        // Release the mutex
        mutex.ReleaseMutex();
    }
}
```

Notice that there’s almost no difference in structure between `Mutex` and `Monitor`. The only notable difference is that we haven’t created an empty `object` instance as a locker. The `Mutex` instance uses itself as this locker object.

The main synchronization is done by the `WaitOne()` and `ReleaseMutex()` methods. The `WaitOne()` method suspends thread execution until the mutex object is obtained.

Initially, the mutex is free, so one of the threads gets it.

After all actions have been completed and the mutex is no longer needed, the thread releases it using the `ReleaseMutex()` method. Then, the mutex is acquired by one of the waiting threads.

When execution reaches a call to `WaitOne()`, the thread waits until the mutex is released. After receiving it, it continues to do its job.

# Synchronization using mutex

The word mutex stands for **mutual exclusion**. It’s a special object that can restrict access to a critical section of the code. In essence, there’s nothing much that separates a mutex from the `lock` statement or the `Monitor` class. We create a mutex object and, whenever we enter a critical section, we acquire the lock for the mutex. If the mutex has already been acquired by another thread, then the thread has to wait until the mutex is released.

> **Note:** The mutex in .NET is represented by a class called `Mutex`, which resides in the `System.Threading` namespace.

Unlike the `lock` statement and `Monitor`, `Mutex` doesn’t need a separate locker object because it serves this purpose itself:


```C#
// Mutex
static Mutex mutex = new Mutex();

static void SomeMethod()
{
    // Critical section begins here
    mutex.WaitOne();
    try
    {
        // Critical section code
    }
    finally
    {
        // Release the mutex
        mutex.ReleaseMutex();
    }
}
```

Notice that there’s almost no difference in structure between `Mutex` and `Monitor`. The only notable difference is that we haven’t created an empty `object` instance as a locker. The `Mutex` instance uses itself as this locker object.

The main synchronization is done by the `WaitOne()` and `ReleaseMutex()` methods. The `WaitOne()` method suspends thread execution until the mutex object is obtained.

Initially, the mutex is free, so one of the threads gets it.

After all actions have been completed and the mutex is no longer needed, the thread releases it using the `ReleaseMutex()` method. Then, the mutex is acquired by one of the waiting threads.

When execution reaches a call to `WaitOne()`, the thread waits until the mutex is released. After receiving it, it continues to do its job.

Explore additional thread synchronization primitives.

Getting Started

C# Programming Basics

Classes and OOP

Classes and OOP II

Exception Handling

First Assessment

Delegates and Events

Interfaces

Additional Features

Collections

LINQ

Working with Strings

Working with Dates and Time

Multithreading and Asynchronous Programming

Reflection

Dynamic Binding

Garbage Collection and Unmanaged Resources

Final Assessment

Next Steps

Appendix

Mutex and Semaphore

Synchronization using mutex