Registering a VB.net dll

I created a VB.net dll and successfully referenced it and got it to work from an Access 2003 application running on the same computer that I used to create the dll by copying the .tlb file from the project's debug folder to the system 32 folder.  Now I'm trying to register the .dll on a different computer (a Server 2008 R2 computer) using regasm.exe in the v4.0.30319 .Net framework folder (Note: the .dll uses framework 4.0) and I'm getting the error "Unable to locate input assembly 'altekvb.dll' or one of its dependencies".  I copied altekvb.dll and altekvb.tlb to the computer's system32 folder and then typed "regasm.exe altekvb.dll /codebase" from the v4.0.30319 folder.  Why do I get this error?
LVL 1
Declan_BasileITAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

Declan_BasileITAuthor Commented:
I found something on the internet that said that I had to copy the dll to the C:\Windows\SysWOW64 folder and that worked, however I received a warning that the assembly should have a strong name.  Is this something that I should address?
Jacques Bourgeois (James Burger)PresidentCommented:
A strong name is a digital signature. It is usually required when the dll is not in the same directory as the application that uses it. It enables the application to check that the dll it calls at runtime is the same as the one that was used when the application was compiled.

You add one to your dll through the Signing tab of the project's Properties window (last entry in the Project menu or double click on My Project in the Solution Explorer).

Check the Sign the assembly checkbox and create a strong name key file in the drop down to that effect. Make sure that you protect it with a password, making good note of the password. In most situations, you will always reuse the same file later on if you need to sign other projects.

You will have to recompile the application that use the dll after the dll has been signed.

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
Declan_BasileITAuthor Commented:
Thanks you.
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.