Automatically detects and repairs stale, missing, or orphaned assembly binding redirects in .NET Framework and .NET (Core) projects.
The Problem
After NuGet updates or partial deployments, binding redirects in web.config / app.config often reference wrong assembly versions, causing runtime errors like:
Could not load file or assembly 'Newtonsoft.Json, Version=12.0.0.0, ...' manifest definition does not match the assembly reference.
Tracking down which redirects are wrong and what versions they should point to is tedious and error-prone. This extension automates the entire process.
Features
Automatic Detection -- scans all projects in your solution for stale, missing, orphaned, or conflicting binding redirects
Multi-Source Version Resolution -- cross-references four independent sources to pinpoint exactly where versions diverge:
NuGet resolved DLL (authoritative)
Package reference version (cross-check)
Physical DLL in bin/ (what is deployed)
Config redirect (what the runtime uses)
One-Click Fix -- update stale redirects, add missing ones, remove orphaned entries, or rebuild projects with conflicting bin/ output
Fix All -- batch-fix all detected issues in a single click
Deprecated Package Detection -- flags packages like Microsoft.Azure.Services.AppAuthentication with migration guidance and offers removal with a warning
Orphaned Redirect Detection -- detects binding redirects with no DLL on disk, distinguishes .NET (Core) (safe to remove) from .NET Framework (verify GAC first)
DLL Project Redirect Cleanup -- detects class library projects where binding redirects have no effect (CLR only reads host app config) and offers bulk removal of the entire section or file
Framework Detection -- reads target framework from .csproj to provide framework-specific guidance
Supports Both Project Types -- works with PackageReference and packages.config projects
Parallel Scanning -- analyses up to 5 projects concurrently with real-time progress ("Analysing 3 of 12: ProjectName...")
Resizable & Sortable Columns -- drag column borders to resize, click headers to sort ascending/descending
Educational UI -- a built-in Background tab explains what binding redirects are, why they break, and how this tool resolves them
Theme-Aware -- fully adapts to Light, Dark, Blue, and High Contrast themes
Non-Destructive -- creates timestamped backups before modifying any config file
Usage
Open a solution containing .NET Framework or .NET (Core) projects with web.config or app.config
Go to Tools > Binding Redirect Fixer
The tool window opens and automatically scans your solution
Review the detected issues in the multi-source grid
Filter by status (e.g. "Orphaned .NET (Core)") to focus on one group
Click Fix Shown Items to resolve all visible issues, or fix them individually
How It Works
The extension reads assembly versions from multiple sources and compares them:
Source
What It Represents
Trust Level
NuGet Resolved DLL
The actual DLL from the NuGet cache
Authoritative
Package Reference
What was requested in .csproj / packages.config
Cross-check
bin/ DLL
What is physically on disk
Can be stale
Config Redirect
What the runtime currently uses
Often wrong
Issue Types
Status
Meaning
Auto-Fix
STALE
Config redirect points to an old assembly version
Updates newVersion
MISSING
Redirect needed but does not exist
Adds dependentAssembly element
CONFLICT
Analysis error (corrupted DLL, inaccessible path)
Manual resolution
DUPLICATE
Multiple redirects for the same assembly
Removes duplicate
MISMATCH
Redirect targets a version not on disk
Removes the redirect
TOKEN LOST
DLL exists but is unsigned while config expects a public key token
Preserves token, updates version if needed
DEPRECATED
Package replaced by a modern equivalent
Removes redirect (with warning)
ORPHANED .NET (Core)
No DLL found in a .NET (Core) project
Removes redirect (safe)
ORPHANED .NET Framework
No DLL found in a .NET Framework project
Removes redirect (verify GAC first)
UNUSED IN LIBRARY
Binding redirect in a class library (DLL) project
Removes all redirects (section or file deletion)
Requirements
Visual Studio 2022 (17.14+) or Visual Studio 2026
.NET Framework or .NET (Core) projects with web.config or app.config
