Yes , you are right but when I disable Bglmanx.dll in dll.xml this module (EZDOK) is working again!
That doesn't mean it's a bglmanx.dll problem.
The most likely source of potential conflict between two modules, is the C++ runtime library that they were compiled with and how they signal to Windows this, by using an embedded manifest file. Our module use the VC++ 2005 (SP1) runtime, which is the same as used by FSX and of course includes a proper manifest file inside to tell Windows about this. Even if this info might not tell much to you, it might be helpful if you report it to EZDOK developers, maybe they'll have an idea what the problem could be.
Another thing you can try, is to rearrange the *order* of the modules in the DLL.XML, this could make a difference.
Rearranging the order of the modules in the DLL.XML did not help.
I reported your advice to EZDOK developer.
But here are my Microsoft Visual C++ 2005 Redistributable status on "Programs and Features" Win7 64:
Microsoft Visual C++ 2005 ATL Update kb973923 – x86 8.0.50727.4053 (250KB)
Microsoft Visual C++ 2005 Redistributable (426KB)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.21022 (2.52MB)
Microsoft Visual C++ 2008 Redistributable – x64 9.0.30729.4148 (788KB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.21022 (3.51MB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148 (596KB)
Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.17 (238KB)