Skip to content

Please strong name your library #153

@AArnott

Description

@AArnott

When referencing this from a strong named assembly, I get this warning:

Referenced assembly 'NetArchTest.Rules, Version=1.3.1.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.

If the test project were targeting .NET only, suppressing this warning would be safe. But when the test runs on .NET Framework, this is a fatal condition that will cause my test assembly to fail to load.

Strong naming a test assembly is required when testing a shipping assembly that is itself strong named and has InternalsVisibleTo extended to the test assembly.

In summary, users who satisfy all the conditions below cannot use this library unless it is strong named:

  1. The assembly under test is strong named.
  2. The assembly under test makes InternalsVisibleTo the test assembly.
  3. The assembly must be tested on .NET Framework.

A broader set of customers are also impacted by this, but the core customers that would require this issue to be resolved are the ones in the above set.

Thanks for the awesome library!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions