Then I get a pop up asking for the executable file. This is where I get lost again. I have tried browsing to the .exe file that the dll would eventually be a part of. But that doesnt help - I wonder if it is because the dll is only used in the app when called upon?
I can't get the blasted .NET Framework 3.5 to install on my computer -- which means that VS won't install either, so I don't know what the dialog box is about.
A DLL is not designed to be executed by itself. It is a dynamic link library -- meaning some other program (EXE or DLL) uses it.
So now you need to write an EXE that uses your DLL.
I appreciate your help - I understand the dll is utilized within an exe file. I linked the debug to the executable file that the dll would run in. But in the audio application the dll would run in its a 'optional" file that needs to be installed. So when I link to the exe file - the program launches - but it has no reference to the dll being debugged.
So I am stuck. I was hoping to be able to compile the sample code from the API kit into the dll - and then start tearing apart the source code to understand how it works.
Any other thoughts?
I will dig through the API manual again and see if there is a contact email for support.