Is there any particular reason to have <xxx>IntegrationEventService implement IDisposable?

Can’t help wondering the purpose of using private volatile bool disposedValue; in every implementation of integration event service, as well as the

       protected virtual void Dispose(bool disposing)
       {
           if (!disposedValue)
           {
               if (disposing)
               {
                   (_eventLogService as IDisposable)?.Dispose();
               }

               disposedValue = true;
           }
       }

       public void Dispose()
       {
           Dispose(disposing: true);
           GC.SuppressFinalize(this);
       }

code snippet. What are they, and is it really necessary to do so?

[nicholasyin]

Well, the integration services are not wrapped in any usings, instead they are used just like any regular injected scoped service in the controller. So I don’t really see the reasoning of implementing IDisposable here.

Furthermore, I’m more confused about the use of volatile boolean variable. Not a clue of why it is done this way.

[nicholasyin]

@sughosneo So why was the dispose mechanism implemented like this? What’s the problem of using the normal way of Dispose method, or even not implementing IDisposable at all? The only thing that will get disposed of, as far as I can tell, is the DbContext for integration event log. Don’t know why this context requires explicit disposal, unlike the regular business DbContext that got injected in many places.