Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6235465
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T10:40:23+00:00 2026-05-24T10:40:23+00:00

i have trouble with building some projects. please consider this scenario: i have 2

  • 0

i have trouble with building some projects.
please consider this scenario:

  1. i have 2 projects. for example A and B.
  2. there is a reference from A to B
  3. project of B was strongly signed (i did not want it to be signed for some reasons. so i decided to remove it`s checkbox of “sign the assembly”)
  4. there was a line of code in
    AssemblyInfo.cs file in the A project says:

    [assembly: InternalsVisibleTo("B,publicKey=0024......")]
    

    i changed it to:

    [assembly: InternalsVisibleTo("B")]

    now when i compile one of
    these projects, an error has came up and says:

Friend assembly reference ‘B’ is invalid. Strong-name signed assemblies must specify a public key in their InternalsVisibleTo declarations.

my question is here: how does compiler know that it was a signed assembly someday? and how can i completely remove strongly signed from assembly of B and finally build them correctly?

edited:
by the way
please note that both of theme is not strongly signed! because i remove both of those “sign the assembly” checkboxes from those project`s properties


when i changed the name of assembly to the some wrong name like “bla_bla_bla” that does not even exists, the error is the same!

[assembly: InternalsVisibleTo("bla_bla_bla")]

i think that this Theory is true:

in fact B Project does not compiled, and if it does not find the matched compiled project name (when building project A), compiler guess that B project is strongly signed with the public key that developer did not provide it! and at last it will prompt such odd error!

for the reason of B has a reference to A, when i compile B project, it will compile it’s reference first (A project) and again compiler will prompt me that error (as the same as when i comopile project A)

but either it`s not true or some thing is wrong with my project A. because i start two new simple projects from scratch and every thing goes fine with no error (even when i change [assembly:…] statement to the invalid assembly name) i completely crashed

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T10:40:24+00:00Added an answer on May 24, 2026 at 10:40 am

    Oh My God! i have to remove this line of code:

    [assembly: AssemblyKeyName("")]

    so that projectA completely forget about signing project and continue it`s easy life

    as you know if the destination Assembly was signed so referenced assembly must be signed too. in fact this line of code remind compiler that this project is signed. so… the target assembly should be signed too. therefore compiler complaint about having friend assembly with no ” , publicKey=…” token.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have trouble finding way to correctly refactor this code so that there would
I have some trouble building a good algorithm. Here is my criteria: I am
I have no trouble building 1.35.0, as well as 1.36.0 on the timesys arm-gcc
I have trouble when designing classes like this class C1 { public: void foo();
I have trouble where, for some reason, SVN would only merge the newly generated
I have some trouble with returning the message popup in mvc3 when some exception
I'm building my first simple Windows Phone app. I'm having some trouble though. I'm
I am building a forum from scratch in PHP. I have used the most
Sorry if this is a basic question - I'm having some trouble making the
Hey, I have some trouble using the stream_publish method, more exactly with the attachment

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.