Error with interop dll

When running a vb.net application installed on another machine than the dev machine  the application gives me the following error:

Com object with CLSID {blabla} is ether not valid or not registered

It happens whenever the app calls an interop com object (eg creates an instance).

Is it really necessary to register the interop com dll, or are there other ways so that registration is not necessary?

If I have to register, do I have to use gacutil or how do I do it?

If the interop.blabla.dll does not have a strong name (name, version, public key), how can I change it so that it has a strong name and can be added to the gac (if necessary at all)?
netsltAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

netsltAuthor Commented:
Additional Question: do I have to register the interop.blabla.dll or the original .dll?
0
Bob LearnedCommented:
The original DLL needs to be registered, just like in the past with COM libraries.  The Interop DLL is a wrapper class that transforms the calls into .NET-understandable calls.  The Interop library can be in the GAC, but the COM library can be anywhere you want it to be, since the location is determined from the Windows Registry.

Bob
0
netsltAuthor Commented:
So there is no other way than registering these dll's?
0
Bob LearnedCommented:
When working with COM libraries, the answer is No.

Bob
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
netsltAuthor Commented:
OK, I configured the installer to register the dll, the app works fine now.

Thanks!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.