This is an old thread, however I recently ran into the same issue. To help other users I am posting the method that worked for me. The whole process was quite fast once I figured out what to do.
I tried using the lib file generated by PB with Visual Studio 2013 and that did not work. I got an unresolved external function even when the linker used the lib file generated by PB. This may be because lib file formats change between different MSVC versions.
I then used Nirsoft's DLL export viewer to view functions exported by the DLL and to ensure that I had not messed anything up. The DLL export viewer gave me the exported function names and their ordinal values (read the Microsoft link further down to figure out the meaning of ordinal numbers)
http://www.nirsoft.net/utils/dll_export_viewer.html
I then created a def file manually using information contained here
https://msdn.microsoft.com/en-us/library/d91k01sh.aspx
The def file is fairly simple and looks like
Code: Select all
LIBRARY BTREE
EXPORTS
Insert @1
Delete @2
Member @3
Min @4
Then using the lib tool available in VS 2013 developer prompt
Code: Select all
lib /machine:i386 /def:testdll.def
I created the lib file.
This worked with VS2013 and I was able to successfully use code written in PB and exported as a dll from C.
I used
to declare exported functions in my PB DLL file. I declared them as
in C code.