2

I have a SingleInstance service that I need to be active very early in my application. However, this service is maintained in a DLL that is consumed by other applications, so I'd prefer that this "early activation" be configured directly in the registration extensions/modules used to register the feature to which it related, rather than forcing the consumer to do a superfluous Resolve operation just to get the feature to work--or put another way, allowing them to forget to do it.

Is there an option in the fluent configuration for SingleInstance services that allows this? Or perhaps an event that I could hook into?

Marc L.
  • 3,296
  • 1
  • 32
  • 42

1 Answers1

2

You should look into implementing IStartable.

Or, as @Travis points out, use the AutoActivate() registration extension. This wraps the registration in an implicit IStartable and thus automatically activates the registration when the container is built.

Peter Lillevold
  • 33,668
  • 7
  • 97
  • 131