C#: best practices for implementing a thread-safe singleton pattern in a multithreaded environment

See more:

C#

.NET

ASP.NET-Core

I'm designing a multithreaded application in C# and need to implement a thread-safe singleton pattern for a shared resource. I've come across various implementations, but I'm unsure which one is the most efficient and scalable.

What are the best practices for implementing a thread-safe singleton pattern in C#? Should I use locking, concurrent collections, or a more advanced approach like the Lazy<t> class?

Here's a basic example of what I'm trying to achieve:

public class Singleton
{
private static Singleton _instance;
private static object _lock = new object();

public static Singleton Instance
{
get
{
// Thread-safe implementation here
}
}
}

What I have tried:

What are the pros and cons of different approaches, and how can I ensure my implementation is both thread-safe and performant in a high-concurrency environment?