It's kind of pointless to write your own IoC container in C# seeing that there'sIt's kind of pointless to write your own IoC container in C# seeing that there's probably a 100 out there at this point. With that said, there are occasions like the project I'm in now where you plan on some point pulling in a popular controller, but you need something basic to register and resolve instances of interfaces throughout the existing code base in the mean time.The idea is this:You have viewModels or controllers that need services, clients, other controllers, whatever.You could just not care about clean code and do this:public class MainViewModel()
{
private readonly IService _service;
private readonly IDataSource _source;
public MainViewModel() {
_service = new Service();
_source = new Source(service);
}
void go() {
_service.CallAPI();
}
}
No big deal. But you start doing this in multiple controllers, viewModels, and then…
Comments
Post a Comment