[lacrue79]

A DLL that was created in VB.net by someone else was sent to me to include in an Excel VBA project. I registered the DLL on my machine using visual studio 2008 tools regasm. Once the DLL was registered in my systems32 folder I tried to reference it in my VBA project but I could not because of errors stating it could not be referenced. Then I found that I didn't even need to reference it. The calls the DLL were working just fine without me having to reference or declare the DLL in my vba project.

Question 1: Why is that? I thought that to use functionality built into a DLL it had to be referenced or declared somehow. I would really like to understand this if possible.

Question 2:Do you foresee any issues with this when releasing to the end users?

Question 3:What is the best way to get the DLL out to multiple end users without having to manually register the DLL myself?