• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 296
  • Last Modified:

Unable to emit assembly: Referenced assembly 'AxInterop.ChargeNet' does not have a strong name

Hey guys!!!

Any ideas on this error in VB.net?

  • 2
1 Solution
Jacques Bourgeois (James Burger)PresidentCommented:
You are trying to compile a signed application that references an unsigned application. This breaks the integrity of the application, so the compiler stops you.

When you compile an application with a strong name (digital signature in the Signing tab of the project's Properties window), all the reference assemblies should also be signed. Security would be compromised otherwise.

Contact whoever provided you with AxInterop.ChargeNet and ask them for a signed version of their assembly.

JDL129Author Commented:

Leave it to me to try to make things hard!!!!!

Jacques Bourgeois (James Burger)PresidentCommented:
You did not make things hard. They are hard as they are :-).

This was one we all get at some time in the first few years, and I will tell you that if they had phrased their error message around digital signature instead of "strong name", everybody would understand it a little more easily.
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.

Join & Write a Comment

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now