I have a dll declared in a module similar to:
Public Declare Function myFunc Lib "mylib" (ByVal i As Long) As Long
The dll is physically located in the same directory that the VB project files are stored & at install where the application is stored. The install works fine but when running from the debugger, VB cannot seem to find my dll. I don't want to register the dll and because we are using Visual Source Safe, I can't use a hard-coded path during debug. (If I do use a hard-coded path, it does work though, so it's not a problem with the dll.)
Also, maybe I'm going about this all wrong?? My VB program uses DLL I wrote in C. Both projects are under version control under Source Safe & are modified on a regular basis. To get the dll to be used by VB, I added the .dll file to the C project in Source Safe and shared it with the VB project. Is this the best way?? Either way I need a solution that allows for both projects to be under version control and allow the dll to be found by Visual Basic.