ThreeMammals/Ocelot

Strong-named binaries

Open

#399 opened on Jun 12, 2018

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

Repository metrics

Stars
 (8,137 stars)
PR merge metrics
 (Avg merge 44d 17h) (6 merged PRs in 30d)

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

Research direction
Add strong name signing to the Ocelot assembly by generating a strong name key file (.snk) and configuring the project to sign the assembly. Update any build scripts or CI/CD pipelines accordingly.
Tech stack
csharp
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75