Move .UseNServicebus to IServiceCollection (Or create seperate exension method)

[moanrose]

Currently it is impossible to choose whether to initialize NServicebus or not based on configuration

I would suggest changing the UseNServicebus extension method, so that it extends IServiceCollection - or create seperate exension method with the following signature

public static void UseNServiceBus(this IServiceCollection serviceCollection, Func<HostBuilderContext, EndpointConfiguration> endpointConfigurationBuilder)

That way you can conditionally initialize NServicebus in ConfigureServices

[danielmarbach]

Hi Morten

Currently it is impossible to choose whether to initialize NServicebus or not based on configuration

Can you add some more context to this. I'm not sure I understand what you mean. Maybe you can write some code snippets and annotate it with comments so that we can see what blockers you are facing?

Thanks
Daniel

[kbaley]

@moanrose Can you describe the scenario this would be used? Are you looking to do something like "if this happens then use NServiceBus, otherwise use this other thing"?

[moanrose]

@kbaley Kyle, it is a bit vague in my memory, but i believe it was one of the latter:

• "Allow me to switch back to my old way of doing things using configuration, if NServicebus or transport gives us problems i production." (Feature flag)
• "If there is no connectivity to my transport upon startup, dont leave my application dead in the water, but use this other thing"

I dont have acces to the codebase, or the backlog anymore