Hi,
I've been attempting to incorporate NLog into a project that mainly consists of components built from unmanaged code (VB6 and C++). The logging components were written in C++; this gave me an opportunity to give NLog's C++ API a go - it has worked pretty well so far but I've encountered a major issue with the VB6 components which make calls into that C++ logging component. For some reason, the inclusion of the NLog C++ API calls disrupts the build process of these VB6 components not during compile time but when the binary is being built.
I realise that this isn't the best of explanations so I'll try to make things a little simpler steps that I've taken:
1. Introduce some NLog C++ API calls into my C++ logging component. Build it.
2. Run my application, it runs and logs (with nlog) fine.
3. Open up a VB6 component. "Make" it's target binary.
4. The build process succeeds (i.e. a new binary is created) but an odd message pops up (such-and-such component could not be loaded) during the binary building stage (i.e. Writing EXE); the new binary is corrupted and cannot function properly.
At this stage it looks like the VB6 IDE doesn't like NLogC.DLL? Has anyone else experienced this and if so, is there a known workaround?
I've also tried to build a .NET component which references NLog.DLL and reference and use it from VB6 without any such problems. So it seems like a problem only with NLogC.DLL.
cheers!
