I've done that three times already and it didn't make a difference.
Main Topics
Browse All TopicsExperts,
I have a .dll that I'm referring to in my main project with two Imports statements referencing its contents. After updating that .dll and rebuilding it successfully, I get the following error:
"namespace or type specified in the Imports BaseCommon.BaseCommonBAL doesn't contain any public member or cannot be found. Make sure the namespace or the type is defined and contains at least one public member. Make sure the imported element name doesn't use any aliaes"
Nothing has changed about the .dll code and it worked about 15 minutes ago. Ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Is it a VB6 DLL?
If so see this:
The two earlier responses might be the cause, but another possibility is related to the interop assembly. An interop assembly is generated by the IDE when you added the reference. This is a managed assembly that exposes the types from the DLL that are consumable in a .Net application. If you change any of you public type signatures, then this DLL will need to be regenerated.
If you'd like to automate this process, take a look at the documentation for TLBIMP. This is the tool that the IDE runs to generate the DLL. You can find it in the SDK folder on your machine. (Something like: C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin)
I hope this helps.
Mike Carter
Visual Basic QA
from : http://social.msdn.microso
General Microsoft comments on the error:
http://msdn.microsoft.com/
Business Accounts
Answer for Membership
by: wrmichaelPosted on 2009-10-22 at 07:27:32ID: 25634596
remove the DLL reference and readd it.