Static classes that require the Initialization method to be called previously used - is everything all right?

Question

In my project, I have several static “service” classes that should be easily accessible throughout the project, and therefore they are static. However, in order to initialize them, I have to pass them data that is only available at startup time, which leads to the fact that the code is similar to this:

public static class VisualStudioEvents
{
    private static Data _data;

    public static void Initialize(Data data)
    {
        _data = data;
    }

    public static void Func()
    {
        AssertInitialized(_data);

        // Code of actual Func() goes here.
    }
}

What do you think about this? Is there any other project that should be applied here? Or is this design acceptable?

Thank!

Answer 1

I would be very comfortable. The only change I would make is to enforce it as soon as:

    public static void Initialize(Data data)
    {
        if (data == null) throw new ArgumentNullException("data");
        if (Interlocked.CompareExchange(ref _data, data, null) != null)
        {
            throw new InvalidOperationException("Already initialized");
        }
    }

oh -I guess Data , .

Answer 2

, , , . , .

, - inversion of control, , . IoC singleton , .

, :

public class VisualStudioEvents
{
    public VisualStudioEvents(VisualStudioEventsConfig config)
    {
        // ...
    }

    // ...
}

VisualStudioEventsConfig, IoC , . VisualStudioEvents .

Answer 3

, , Singleton, Data , , Data .

, Data , , / .

Answer 4

VisualStudioEvents , API Visual Studio.

, VisualStudioEvents - , . . - .

edit: , , , . , , , component. static cling .

Answer 5

Instead of a static class, you can try using a singleton pattern . This would also make code verification easier.