The thing is, Andry, I am a bit new to VB.NET myself. I'll take my best
shot, but it is the newbie advising the newbie.
If I were having the same problem, I would try to debug it first on my
development machine. Have you tried that? Can you successfully access/use
your dll there?
Assuming that you have success on the development machine, you can note the
registry entries. This will allow you to see what is missing on the target
machine.
My guess would be that the registry is not correctly set up on the target
machine.
I didn't explicitly mention the *.tlb, but the msi must be set up to
register that as well.
If the registry is set up correctly, I suppose the framework could be the
problem. Is the .NET framework set up right on the target? There are ways
to distribute it yourself, but in my case I simply make it a prerequisite
that the users must install themselves. If they don't, executing the msi
prompts them.
That is about the extent of what a fellow newbie can recommend. If the
problem persists you might post back here or in a new thread with as much
detail as you can.
Regards,
Ot