icsharpcode/ILSpy

How to deal with assembly binding redirects?

Open

#1,508 opened on May 4, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (3,645 forks)batch import
EnhancementHelp Wanted

Repository metrics

Stars
 (25,162 stars)
PR merge metrics
 (Avg merge 15d 22h) (61 merged PRs in 30d)

Description

Larger applications consisting of multiple assemblies these days usually have binding redirects in place. As far as I can tell this leads to ILSpy not being able to resolve references (or sometimes pulling in duplicate assemblies with different versions from the GAC) and generally a lower quality of the decompiled code.

Am I missing anything in how to deal with assembly-setups requiring binding redirects? Otherwise I think its time to consider this as a new feature, going forward with nuget based packaging I think redirected bindings will become much more common than they were in the past.

Contributor guide

Research direction
Explore how ILSpy currently resolves assemblies and design a method to read assembly binding redirects from configuration files (e.g., app.config or runtime config) to improve decompilation accuracy.
Tech stack
csharp
Domain
developer experience
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-2 days
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.
Mostly clear
Prerequisites
C#.NETAssembly loading
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65