In my opinion it just inverses the inversion and could make new users (including myself) make incorrect assumptions about using IoC containers.It can be used for the Service Locator (anti-)pattern of course, but it doesn't sound like a strong reason to me (can be a separate class in the end of the day).There probably will be at least one call to get the root object to start the program, but it could be named and designed (signature and contract) accordingly to avoid calling it for more than one reason.I am more interested in single-point of entry classic apps rather than server-side web apps.
Why do IoC containers provide public Resolve method(s)?
design;dependency injection;anti patterns;ioc;ioc containers