.NET多版本同DLL解决方案自动部署Pipeline及冲突解决咨询

This is a super common pain point in .NET development, and there are standard, maintainable ways to fix it without resorting to manual GAC installs or bloating your repo with packages. Here's what you should do, depending on your .NET version:

1. Binding Redirects (Best for .NET Framework) #

Binding redirects are the go-to solution for .NET Framework projects. They tell the CLR to use a single version of an assembly regardless of which version individual projects reference.

How to set this up: #

• Auto-generate redirects: Right-click your executable project (the one that gets deployed) → Properties → Build → Check "Auto-generate binding redirects". Visual Studio will automatically add the necessary entries to your app.config or web.config during build.
• Manual setup: If you need more control, add entries directly to your config file:

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="YourAssemblyName" publicKeyToken="your-public-key-token" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.1.0.0" newVersion="2.1.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  

This ensures all references to any version between 0.0.0.0 and 2.1.0.0 are redirected to 2.1.0.0.

2. Centralized Package Management (Best for .NET Core/.NET 5+) #

Modern .NET versions (Core/5+) use PackageReference by default, which makes version unification straightforward. The key is to enforce a single version of each package across your entire solution.

How to set this up: #

• Create a Directory.Build.props file at your solution root. This file will apply settings to all projects in the solution.
• Add entries to define the version of each conflicting package:

  <Project>
    <PropertyGroup>
      <!-- Define versions centrally -->
      <YourAssemblyVersion>2.1.0.0</YourAssemblyVersion>
    </PropertyGroup>
    <ItemGroup>
      <!-- Reference the package with the centralized version -->
      <PackageReference Include="YourAssemblyName" Version="$(YourAssemblyVersion)" />
    </ItemGroup>
  </Project>
  

All projects in your solution will now use the same version of the package, eliminating conflicts before deployment even happens.

3. Side-by-Side Deployment (If You Need Multiple Versions) #

If you absolutely must run multiple versions of the same assembly (e.g., different parts of your app depend on incompatible versions), you can use the <codeBase> element in your config file to specify where each version lives.

Example: #

<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
      <assemblyIdentity name="YourAssemblyName" publicKeyToken="your-token" culture="neutral" version="1.0.0.0" />
      <codeBase href="v1/YourAssemblyName.dll" />
    </dependentAssembly>
    <dependentAssembly>
      <assemblyIdentity name="YourAssemblyName" publicKeyToken="your-token" culture="neutral" version="2.1.0.0" />
      <codeBase href="v2/YourAssemblyName.dll" />
    </dependentAssembly>
  </assemblyBinding>
</runtime>

Then deploy each version to its own subdirectory (v1, v2, etc.). Note that this adds complexity to your deployment pipeline, so only use this as a last resort.

Why Your Current Approaches Are Less Than Ideal #

• Manual GAC installs: This is not scalable—you'll have to repeat the process every time you deploy or update the assembly. It also risks conflicts with other applications on the server that might use a different version.
• Checking in the packages folder: This bloats your version control repo with large binary files, leads to merge conflicts, and makes your repo slower to clone. It's a maintenance nightmare for large teams.

Quick Recap #

• For .NET Framework: Use auto-generated binding redirects to unify versions.
• For .NET Core/.NET 5+: Use centralized package management to enforce consistent versions across all projects.
• Only use side-by-side deployment if you can't avoid running multiple versions.

内容的提问来源于stack exchange，提问作者WilsonPena