Unable to emit assembly: Referenced assembly 'cErrorReport' does not have a strong name

I have created a solution in Visual Basic .Net which includes several different class libraries which I created myself.  One of these class libraries is cErrorReport.  At one point I had to change the Namespace name in cErrorReport from ErrorReport to Buck.BASK.Business.DataManager.Errror.Report.  I'm not sure if that's what's creating the error which I mention in the title line.  I'd like specific steps on how to correct this error.  When going to the Visual Basic .Net help file, I got this message:

To correct this error

Examine the quoted error message and take appropriate action.
If the error persists, gather information about the circumstances and notify Microsoft Product Support Services.


This does not help me correct the error.  If anybody knows the specific steps to follow, please respond here.
BKaporchAsked:
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.

testnCommented:
If you use your component in Enterprise Services (COM+), everything must be signed....
http://www.gotdotnet.com/team/xmlentsvcs/esfaq.aspx#6.6

Maybe I'm wrong but I guess you have to sign the assembly...

http://samples.gotdotnet.com/quickstart/howto/doc/sharedname.aspx

If not, I think when you change the namespace, you still have the old dll somewhere. Try to delete all old dll and recompile everything.

0
_TAD_Commented:


eh...


you just need to create a strongly named assmebly.

here's a link:
http://www.c-sharpcorner.com/Code/2003/March/StrongNamedAssemblies.asp



In a nutshell, you need to register your assembly in the GAC (Global Assembly Cache) with a version number and away you go!


Interesting thing about .NET....


Microsoft claims to have solved DLL Hell with .Net, but they introduced GAC Hell.  I don't see it as being any better.

Anywho.... that's just my two cents worth.
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
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
.NET Programming

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.