Refernce Problems post signing the assemblies

Question

1.00/5 (1 vote)

See more:

Hello,

I am relatively new to these stuffs and have been running into the below problem.

I have had the code for an application in C# which used to build and run as expected. It referenced a dozen of C++\CLI assemblies, which resided in the application's local directories.

Now, the referenced C++\CLI assemblies were strong named by it makers. We too strong named our C# assemblies. Upon building, we are experiencing a lot of errors of the type,

Error 56 The name 'ABCD' does not exist in the current context.

I have made sure, we are referencing the correct C++/CLI assemblies in the correct path. If I revert and resuming the non-signed assemblies.. All is well. Thus, this appears to be a problem only with signed assemblies.

Any help is greatly appreciated.

Thanks in advance.

Posted 12-Sep-14 4:45am

StarkBoy

Add a Solution

Comments

Sergey Alexandrovich Kryukov 12-Sep-14 10:49am

Not enough information. You have to find all your ABCDs yourself — due to wonderful fall weather, my access to your hard drive is somewhat limited. I believe you have to have all referenced assemblies also signed, otherwise environment wont allow to build your signed assembly using them. (Well, this makes perfect sense: having a single unsigned assembly would defeat the purpose of signing.)
—SA

KarstenK 13-Sep-14 2:56am

Check for the complete using of the needed namespace.

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)