Kris Jusiak

Thanks, @Oneibus. You make take a look into runtime injector extension which doesn't require templates at all: * https://github.com/boost-experimental/di/blob/cpp14/extension/include/boost/di/extension/injector.hpp * https://github.com/boost-experimental/di/blob/cpp14/extension/test/injector.cpp Then you can simply use it as follows: ```cpp...

Right, that's was by design. Anyway, this issue will go away with DIv2 where named parameters using macros will go away (including .named). Instead, a strong typedef named library will...

That's true, runtime injector was just an experiment as an extension. but it seems to be popular, hence, let me improve the quality of it, sorry for the delay.

I can neither confirm nor deny regarding 16.6.5 version. Tested MSVC versions on CI are passing with both C++14 and C++17 though :thinking: * https://ci.appveyor.com/project/boost-ext/di * v16.6.3 * v16.6.0-pre.1.0

Almost there with https://github.com/boost-experimental/di/pull/465

Is just `di`, okay/available? On vcpkg it is https://github.com/microsoft/vcpkg/tree/master/ports/boost-di

Yeah, `boost-di` would be great, wasn't sure if that's an option? 1. boost-di 2. di 3. ?

Hi @CyberDani, Thanks for the question. Unfortunately, due to C++ not having `universal` templates (NTTP vs types), the exact syntax is not supported ATM. However, it works if inject and...

you can use `[di::override]` in any module to force resovling to the specific binding. For example, ``` di::bind().to() [di::override] ``` should do it

you could use annotations for that - https://github.com/boost-ext/di/blob/cpp14/example/annotations.cpp or strong type interfaces