How can I bind an interface to a class decided by an xml or database configuration at the launch of the application?

I’m re-working on the design of an existing application which is build using WebForms. Currently the plan is to work it into a MVP pattern application while using Ninject as the IoC container.

Ninject/DI: How to correctly pass initialisation data to injected type at runtime

I have the following two classes:

Ninject/DI: How to correctly pass initialisation data to injected type at runtime

I have the following two classes:

Ninject/DI: How to correctly pass initialisation data to injected type at runtime

I have the following two classes:

What is a good practical example demonstrating an architectural advantage in interface dependency injection

I need help (preferably by way of a practical example) to understand why/if the following implementation of IoC/DI (in this case using Ninject) provides an architectural advantage: