Click here to Skip to main content
15,793,547 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:

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.
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.)
KarstenK 13-Sep-14 2:56am    
Check for the complete using of the needed namespace.

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

CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900