Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

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

Posted on 2003-12-02
2
1,007 Views
Last Modified: 2007-12-19
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.
0
Comment
Question by:BKaporch
2 Comments
 
LVL 18

Expert Comment

by:testn
ID: 9857816
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
 
LVL 22

Accepted Solution

by:
_TAD_ earned 500 total points
ID: 9859355


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

Featured Post

Space-Age Communications Transitions to DevOps

ViaSat, a global provider of satellite and wireless communications, securely connects businesses, governments, and organizations to the Internet. Learn how ViaSat’s Network Solutions Engineer, drove the transition from a traditional network support to a DevOps-centric model.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

IP addresses can be stored in a database in any of several ways.  These ways may vary based on the volume of the data.  I was dealing with quite a large amount of data for user authentication purpose, and needed a way to minimize the storage.   …
The object model of .Net can be overwhelming at times – so overwhelming that quite trivial tasks often take hours of research. In this case, the task at hand was to populate the datagrid from SQL Server database in Visual Studio 2008 Windows applica…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question