Beta 5 - Services does not expose IServiceCollection

[jpiell]

While the TestServiceProvider now inherits the IServiceCollection Interface, the IServiceCollection interface is not exposed to the client, leaving the client with no way to register services.

Please expose a property that will return the IServiceCollection.

var modal = new Mock();
Services.AddService(modal.Object); <--- No longer valid.

In addition if you expose IServiceCollection:

services.AddTelerikBlazor(); will be exposed <--- Needed for TelerikGrid

AddScoped
AddSingleton

etc

[egil]

Those Add* methods are part of the Microsoft.Extensions.DependencyInjection namespace. Let me update the release notes to make it clear you need to add that now.

Import that in your .cs or .razor file and you are good to go:

using Microsoft.Extensions.DependencyInjection;

[egil]

Please expose a property that will return the IServiceCollection.

I am not sure why there is a need for an explicit IServiceCollection to be exposed. Due to inheritance, the TestServiceProvider is one, so it should not be needed. See my coding example in the related issue (#38)

[jpiell]

I am still getting:

Severity Code Description Project File Line Suppression State
Error CS1061 'TestServiceProvider' does not contain a definition for 'AddService' and no accessible extension method 'AddService'

[egil]

Thats because there is no AddService any more. You need to call AddSingleton now, which is an extension method from Microsoft.Extensions.DependencyInjection.

Before beta-5, TestServiceProvider was not a true IServiceCollection, thus it implemented a bunch of AddServices methods. That is now changed, and we rely on the from extension method from Microsoft.Extensions.DependencyInjection.

I am sorry if that was not clear enough in the release notes