ThreeMammals/Ocelot

Strong-named binaries

Open

#399 opened on Jun 12, 2018

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (8,137 stars) (1,617 forks)batch import
featuregood first issuehelp wantedmedium effort

Description

Expected Behavior / New Feature

Ocelot binary (ocelot.dll) is not strong-named

Actual Behavior / Motivation for New Feautre

Ocelot cannot currently be consumed from strong-named projects. Projects that are strong-named must reference only strong-named dependencies, so Ocelot would have to be strong-named too,

Specifications

  • Version: 7.0.5

Contributor guide

Tech stack
csharp
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of .NET strong namingFamiliarity with .csproj files
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine the Ocelot main project file (e.g., src/Ocelot/Ocelot.csproj) and add a `<StrongName>` property or set the `AssemblyOriginatorKeyFile` property. Generate a strong name key file if not present. The issue has no linked PRs or maintainer comments; the change should be straightforward and localized.