title: Strange VB6 build problems (related to nlog)
body: <p>This I think is related to my use of the nlog C++ API (and my question on the nlog forum is <a href="http://www.nabble.com/NLogC-problems-with-VB6-IDE-tt19662300s6167.html" rel="nofollow noreferrer">here</a>); the purpose of my asking this question here is to get a wider audience to my problem and perhaps to also get some more general ideas behind the VB6 IDE's failure to build in my particular scenario.</p>
  
  <p>Briefly, the problem that I am having is that I am having trouble building VB6 components which reference unmanaged C++ components which have calls to nlog's C\C++ API (which is defined in NLogC.DLL). The build problems are not occurring during compile time, they are occurring when the binary is being built which suggests to me that it's some kind of linker type problem? Don't know enough about how VB6 binaries are produced to tell. The VB6 binary is produced, but it is corrupted and crashes shortly after it is invoked.</p>
  
  <p>Has anyone had any similar experiences with VB6 (doesn't have to be related to nlog or C++)? </p>
  
  <p>edit: Thanks for all the responses to this rather obscure problem. Still no headway unfortunately; my findings since I posted this:</p>
  
  <ol>
  <li>'Tweaking' the compile options doesn't appear to help in this problem.</li>
  <li>Adding a reference to the nlog-enabled C++ component from a 'blank' VB6 project doesn't crash it or cause weird build problems. So it isn't a 'native' VB6 issue, possibly an issue with the interaction between nlog and the various components and 3rd party libraries used by other referenced components?</li>
  <li>As for C++ calling conventions: the nlog-enabled C++ component is - as far as I can see - compliant to these conventions and indeed works fine when referenced by VB6 as long as it is not making any nlog API calls. Not sure if the nlogc.DLL itself is VB6 compliant but I would have thought that that is immaterial since the API calls are being made from the C++ component; VB6 shouldn't know or care about what the C++ component is referencing (that's as far as my understanding on this goes...)</li>
  </ol>
  
  <p>edit2: I should also note that the error message obtained during build is: "Errors during load. Please refer to "xxx" for details". When I bring up the log file, all that there is in there is: "Cannot load control xxx". Interestingly, all references to that particular control disappears from that particular project resulting in compile errors if I were to try to build again.</p>