I would not call it Dependency “Injection” at how it works it’s more like Dependency “Retrieval”. In net core they made a great job and here, well, it is cool and works, but it is not automatically satisfied in the constructor. All in all your videos are just great and neat. You gained a new subscriber
Thanks James! It’s great to get some clarity for both platform specific and custom interfaces, as well as understanding the best approach given the imminent launch of Maui. Thanks again!
I prefer using Microsoft.Extensions.DependencyInjection, with the Generic Host. It takes some more plumbing, but it works well. The main drawbacks of Xamarin.Forms are that there are different service providers for Dependencies and for XF infrastructure - different containers. This means that you cannot inject your own services into, for instance, a view or a markup extensions. A workaround is to declare static that is being set in App.cs. I don't know whether, or not, Maui will consolidate all to one container and service provider now when they use the Host Builder.
Beautiful presentation as usual, thanks greatly. May I humbly request you make an IOS version of the Toast please or point us to materials on that, its greatly required! Thank you
What if i want to implement 2 (or more) instances of service from interface, how can i use this? Example: FileLogger and MailLogger form ILogger or MS-SQL and SQLite from IDatabase.
You could used a typed interface most likely to get a specific one back. Normally this isn't the case you have an interface for a specific service. When you ask for an interface implementation back you get a single one. You could not use interfaces and just register the class itself.
what is the point of injecting not through a constructor? DI is needed for convenient testing. How to cover an object with tests, where dependencies are resolved not through the constructor/property but through DependecyService.Get inside object? Covering code with DependecyService with tests is more difficult and imposes a lot of restrictions than code with a constructor
When I think of Dependency Injection it is a broad topic: service locator, container, inversion of control, dependency resolution, construction injection... aka there are a lot of words and different features that developers like. I like to document what is in the box for devs to use. As i mentioned at the end there are a lot of libraries out there and even a way to use the new HostBuilder model(which .NET MAUI will use) in your Xamarin.Forms apps today montemagno.com/add-asp-net-cores-dependency-injection-into-xamarin-apps-with-hostbuilder/
So I have two questions ... 1) Should I be using .NET Core DI instead of Xamarin for future proofing ? 2) How do I implement a view model locator with Xamarin DI ?
I have created my interfaces and classes in another .net standard class library and added refernce to xamarin forms project and DependencyService.Get returns null
Nice video! Question though: If I'm calling DependancyService.Get() inside the class itself, then how can you inject the dependancy later, when unit testing the class, for example? I might be missing something but it seems like the injection part is missing in this kind of implementation of the dependancy injection.
So, would probably look at using Microsoft.Extensions -> montemagno.com/add-asp-net-cores-dependency-injection-into-xamarin-apps-with-hostbuilder/ this will be in to .NET MAUI and has it built in. Autofac can totally also be used like I said at the end. I like to show off what is included in the box.
.NET MAUI will actually use the same DI as those! YOu can use it today if you desire -> montemagno.com/add-asp-net-cores-dependency-injection-into-xamarin-apps-with-hostbuilder/
I don't see how this way of getting services from DependencyService can be considered dependency injection. There is no injection happening here. This seems more of a service locator to me.
When I think of Dependency Injection it is a broad topic: service locator, container, inversion of control, dependency resolution, construction injection... aka there are a lot of words and different features that developers like. I like to document what is in the box for devs to use. As i mentioned at the end there are a lot of libraries out there and even a way to use the new HostBuilder model(which .NET MAUI will use) in your Xamarin.Forms apps today montemagno.com/add-asp-net-cores-dependency-injection-into-xamarin-apps-with-hostbuilder/
@@JamesMontemagno I read your blog post and I also believe that if proper dependency injection is required, generic hosts are the way to go. However, afaik service locator pattern is not an approach to dependency injection. Dependency injection and service locator are two different approaches to dependency resolution and decoupling. I believe this is the reason "dependency injection" is not mentioned in the official documentation of DependencyService at all. Here is a great article that explains the differences between the two patterns: martinfowler.com/articles/injection.html#ServiceLocatorVsDependencyInjection
HI MR JAMES var imageData = await AzureStorage.GetFileAsync(ContainerType.images, urlp); ImgX.Source = ImageSource.FromStream(() => new MemoryStream(imageData)); THAT IS FOR IMAGE>> WHAT ABOUT VIDEO FROM AZURE BLOB STORAGE HOW CAN I PLAY VIDEO FROM AZURE BLOB STORAGE SECURE
