Assembly generation failed

Question

0.00/5 (No votes)

See more:

I m getting this error when i build my project,"Assembly generation failed -- Referenced assembly 'BLL' does not have a strong name."
What does this error mean? and what i hav to do?

Posted 30-Aug-12 0:50am

Dhivyaj

Add a Solution

Comments

Timberbird 30-Aug-12 7:47am

Please see my comment to a solution below

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Kashinath Patil · Answer 1 · 2012-08-30T00:54:00

you have unambiguously signed the Reports.dll correctly from the command line, VS still says that that dll is unsigned; then it must be referencing the wrong file.

If you want to be really paranoid and double-check the strong-naming after signing, load Reports.dll into ildasm (you have to double-click the manifest node in the tree and scroll down to find the .publickey section). Or for ease just open it in ILSpy.

After signing reports.dll; open your referencing project's proj file as an XML document (if you have the VS PowerCommands you can right-click and 'Edit Project File'; otherwise you can unload the project and then open it in VS using the 'Open With' command from the Open File dialog) and verify that the reference to the dll is indeed the correct path. If it's not, correct it and reload the project.

Dhivyaj · Answer 2 · 2012-08-30T21:36:00

Solution 2

Thank you...This issue resolved wen i unchecked "Sign the assembly" in the project properties.

Posted 30-Aug-12 21:36pm