DotNet dll loading compatability

[Crash]

I am trying to build a project using MS VC++ 6.0 using headers, libs,
and dlls that were built on a DotNet IDE. The company that sent me the
lib's and dll's said I can't use them with MS VC++.

Do you agree?

Here's the situation:
After building my own C++ project on MS VC++ 6.0 and including the new
headers and libs from The Company - I came across a runtime error that
popped up a dialog box which said, "shm_create() could not be found in
libbasicff.dll"

I looked in the dll's that were delivered to me and sure enough the
shm_create function is not in libbasicff.dll - rather it is in
libalfast.dll. Apperently, the dll's are supposed to automatically
load by virtue of using #include "libalfast.h" and adding lib's into
my project's linking. So I have 2 libs: libalfast.lib libbasicff.lib
linking in.

Does this sound right to any of you? Just because I'm using VC++ 6.0
that I should get an unresolveable function inside the wrong dll?

Is there a way to explicitly tell my project that the function
shm_create() is in the other dll?

Thanks to all who comment !

 

[Olaf Baeyens]

I am trying to build a project using MS VC++ 6.0 using headers, libs,

and dlls that were built on a DotNet IDE. The company that sent me the
lib's and dll's said I can't use them with MS VC++.

Do you agree?

Is there any reason why you stay with VC++ 6.0?
That thing is ancient.