Services and Dependency Injection pitfalls
In your MVVM journey, DI plays a crucial role in providing essential functionality to your application. However, even in the world of DI, there can be pitfalls waiting to catch you off guard. This section is dedicated to unveiling the most common pitfalls and equipping you with the knowledge to navigate them effectively.
Unable to resolve service for type
A System.InvalidOperationException stating Unable to resolve service for type … is one of the most frequent exceptions when working with DI. The cause is pretty simple: we ask the DI container to resolve an instance of an object that has some dependencies that can’t be resolved. In other words, we haven’t registered all dependencies for this class. Figure 14.2 shows what this exception would look like if we didn’t register the RecipesOverviewViewModel in the DI container:
Figure 14.2: InvalidOperationException thrown
The exception...
