One of the things that most of my customers find challenging when moving to the cloud, is the whole pricing model. They have a hard time finding out what the cost of moving to a cloud platform like Windows Azure would be. Therefore Microsoft introduces the Windows Azure platform TCO calculator, and in 10 minutes or less, you’ll see how Windows Azure compares to on-premises solutions, quantify migration costs, and get a pricing overview.
A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...