Today if one tries to add a custom service to the configuration.Services bag, it will throw exception saying that it does not support unknown services.
We should open this up so that people don't have to use configuration.Property bag to store those config wide settings. Also, because we will use DI first, custom service type will get the benefit.
Comments: Comment from RaghuRam: This bug was created during OData V1 time frame when we said “no core runtime changes”. OData had to add some custom extensibility points at the config level that time and our service container is not really designed for that. We had to use configuration.Properties to store these custom services and this idea seemed good at that time. We no longer have that problem now (inability to modify runtime). So, this bug is not relevant anymore. Also, opening up configuration.Services for general purpose DI would cause more confusion regarding scoping and caching as mentioned in the bug’s comments.
We should open this up so that people don't have to use configuration.Property bag to store those config wide settings. Also, because we will use DI first, custom service type will get the benefit.
Comments: Comment from RaghuRam: This bug was created during OData V1 time frame when we said “no core runtime changes”. OData had to add some custom extensibility points at the config level that time and our service container is not really designed for that. We had to use configuration.Properties to store these custom services and this idea seemed good at that time. We no longer have that problem now (inability to modify runtime). So, this bug is not relevant anymore. Also, opening up configuration.Services for general purpose DI would cause more confusion regarding scoping and caching as mentioned in the bug’s comments.