For cross-process locking in C#/.Net, you can use a named system Mutex.
More Related Contents:
- Why is lock(this) {…} bad?
- Volatile vs. Interlocked vs. lock
- Concurrent HashSet in .NET Framework?
- Asynchronous locking based on a key
- Re-entrant locks in C#
- Is Task.Factory.StartNew() guaranteed to use another thread than the calling thread?
- Is it OK to use a string as a lock object?
- Does a locked object stay locked if an exception occurs inside it?
- How expensive is the lock statement?
- Monitor vs lock
- lock keyword in C#
- What are the differences between various threading synchronization options in C#?
- Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
- C# manual lock/unlock
- Throw a NullReferenceException while calling the set_item method of a Dictionary object in a multi-threading scenario
- Why does the lock object have to be static?
- When is ReaderWriterLockSlim better than a simple lock?
- Why is it a bad practice to lock the object we are going to change?
- Guidelines of when to use locking
- Starting Tasks In foreach Loop Uses Value of Last Item [duplicate]
- Is there a way to indefinitely pause a thread?
- Thread safety of a Dictionary with multiple concurrent readers and no writers
- How do I implement the Sieve Of Eratosthenes using multithreaded C#?
- What’s the least invasive way to read a locked file in C# (perhaps in unsafe mode)?
- ThreadPool not starting new Thread instantly
- Solve a cross-threading Exception in WinForms
- Parallel doesnt work with Entity Framework
- Is Stopwatch.ElapsedTicks threadsafe?
- ReaderWriterLock vs lock{}
- How to work threading with ConcurrentQueue