web-dev-qa-db-fra.com

Comment résoudre les conflits de version de package .NET Core

Je migre d'une application Web .NET MVC 5 vers un projet d'API Web .NET Core 2.2 avec cinq projets .NET Standard 2.0 tous hébergés sous une seule solution.

Je reçois maintenant 28 avertissements (MSB3277) concernant les conflits de packages, qui se trouvent tous dans l'espace de noms System. Par exemple, il semble y avoir un conflit de version pour System.Collections.Concurrent entre Version=4.0.11.0 et Version=4.0.14.0 (voir bloc d'erreur ci-dessous).

Dépannage tenté:

  1. J'ai essayé de désinstaller tous les SDK .NET Core que je n'utilise pas et j'ai actuellement 2.2.300 installée. Cela n'a pas fonctionné.
  2. J'ai essayé d'entrer dans NuGet au niveau de la solution pour installer l'assembly manquant, mais 4.0.14 n'est même pas disponible dans la liste de sélection. Je peux choisir parmi les versions suivantes: 4.3, 4.0.12, 4.0.10 et 4.0.0. J'ai essayé d'installer 4.3 dans tous les projets, mais cela n'a pas fonctionné.
  3. D'autres solutions sur le Web semblent recommander de descendre une version sur le SDK ou de coder en dur une référence dans le fichier * .csproj - ni l'une ni l'autre que je préfère faire si je n'ai pas à le faire. Je n'aime pas le premier parce qu'il semble contre-intuitif de reculer et je n'aime pas le second parce que coder en dur un correctif pour utiliser en permanence un ancien paquet, ce qui semble être une très mauvaise idée car il semble peu probable qu'il le fasse mise à jour vers des versions plus récentes qui seront publiées.

Quelqu'un sait-il comment résoudre ces avertissements? Toute aide est grandement appréciée.

Sortie détaillée sur build pour l'un des avertissements: 

Line 5419: 3>    Dependency "System.Collections.Concurrent, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Line 5420: 3>        Could not resolve this reference. Could not locate the Assembly "System.Collections.Concurrent, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". Check to make sure the Assembly exists on disk. If this reference is required by your code, you may get compilation errors.
Line 5675: 3>    There was a conflict between "System.Collections.Concurrent, Version=4.0.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Collections.Concurrent, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Line 5675: 3>    There was a conflict between "System.Collections.Concurrent, Version=4.0.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" and "System.Collections.Concurrent, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
Line 5676: 3>        "System.Collections.Concurrent, Version=4.0.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "System.Collections.Concurrent, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not.
Line 5676: 3>        "System.Collections.Concurrent, Version=4.0.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was chosen because it was primary and "System.Collections.Concurrent, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" was not.
Line 5677: 3>        References which depend on "System.Collections.Concurrent, Version=4.0.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [C:\Program Files\dotnet\sdk\NuGetFallbackFolder\netstandard.library\2.0.3\build\netstandard2.0\ref\System.Collections.Concurrent.dll].
Line 5677: 3>        References which depend on "System.Collections.Concurrent, Version=4.0.11.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" [C:\Program Files\dotnet\sdk\NuGetFallbackFolder\netstandard.library\2.0.3\build\netstandard2.0\ref\System.Collections.Concurrent.dll].

Mise à jour

Plus de dépannage:

https://github.com/dotnet/standard/issues/731

https://github.com/dotnet/corefx/issues/32561

Est-ce un bug Microsoft?

Sortie minimale lors de la construction répertoriant les 28 avertissements: 

3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Collections.Concurrent" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Collections" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Collections.NonGeneric" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.ComponentModel" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Diagnostics.Debug" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Diagnostics.Process" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Diagnostics.Tracing" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.IO.FileSystem" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Linq" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Net.Primitives" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Net.Security" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Resources.ResourceManager" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Runtime" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Runtime.Extensions" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Runtime.InteropServices.RuntimeInformation" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Security.Cryptography.Algorithms" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Security.Cryptography.Csp" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Security.Cryptography.Encoding" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Security.Cryptography.Primitives" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Security.Cryptography.X509Certificates" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Text.Encoding.Extensions" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Text.RegularExpressions" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Threading" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Threading.Tasks" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Threading.ThreadPool" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Threading.Timer" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets(2106,5): warning MSB3277: Found conflicts between different versions of "System.Memory" that could not be resolved.  These reference conflicts are listed in the build log when log verbosity is set to detailed.
c#visual-studioasp.net-core.net-assemblyconflicting-libraries
18
J Weezy

Le problème est ici une dénomination forte et des versions d'assembly mixtes pour au moins "System.Collections.Concurrent", mais probablement pour l'ensemble des 28 avertissements.

J'ai essayé d'entrer dans NuGet au niveau de la solution pour installer l'assembly manquant, mais 4.0.14 n'est même pas disponible dans la liste de sélection.

Les versions que vous voyez sont les versions NuGet, et ce ne sont pas les mêmes que les versions Assembly. par exemple. La version 4.3.0-preview1-24530-04 de NuGet a la version 4.0.13.0 de l'assembly pour la norme 1.3 .NET:

Veuillez noter que dans le même package, la version Assembly pour netcore50 est 4.0.10.0!

Est-ce un bug Microsoft?

Non, c'est une fonctionnalité. Lorsqu'un assembly est nom fort ., La version complète doit correspondre. Sinon, cela donnera un avertissement. Lorsque vous n'utilisez pas le GAC, alors une seule version de l'Assemblée peut être publiée - alors laquelle si plusieurs versions sont utilisées? Remarque: tous les assemblages de Microsoft portent un nom fort.

Le problème ici:

  • Vous incluez un assembly (fort nommé) qui est construit pour System.Collections.Concurrent Assembly version 4.0.14.0
  • Vous utilisez (indirectement) dans votre application Assembly version 4.0.11.0 pour l'assembly System.Collections.Concurrent.

Donc deux versions pour une seule Assemblée!

Solutions

Il existe plusieurs solutions possibles:

  1. Utilisez partout la même version Assembly pour System.Collections.Concurrent (vous devez savoir quel package NuGet est Assembly version 4.0.14.0). C'est la plupart du temps impossible.
  2. Installez les versions 4.0.11.0 et 4.0.14.0 dans le GAC - ce n'est pas une option vraiment populaire non plus de nos jours -> Pas possible pour .NET Core car il n'y a pas de GAC pour .NET Core. Voir Existe-t-il un équivalent GAC pour .NET Core?

  3. Utiliser un <bindingRedirect> dans votre .config. Voir Redirection des versions d'assembly | Microsoft Docs

    par exemple. pour "System.Collections.Concurrent":

    <dependentAssembly>
    <assemblyIdentity name="System.Collections.Concurrent" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
    <bindingRedirect oldVersion="4.0.0.0-4.0.14.0" newVersion="4.0.11.0" />
</dependentAssembly>

Notes finales

Il existe 28 problèmes de version, mais il y a un grand changement: plusieurs problèmes sont résolus avec un seul bindingRedirect. Donc, le meilleur moyen est de commencer par un (de préférence le plus haut niveau), de reconstruire et de répéter jusqu'à ce que tous soient résolus.

Veuillez également noter que la rétrogradation d'un assembly est un peu délicate, par exemple, l'assembly construit sur 4.0.13.0 pourrait utiliser une fonctionnalité introduite/modifiée dans 4.0.11.0+. Vous pouvez donc également mettre à jour votre version et utiliser cette version dans l'attribut "newVersion"

9
Julian

Redirection de liaison (bindingRedirect) pour chaque assembly, vous pouvez le faire manuellement dans la configuration ou il existe une option dans les propriétés du fichier de projet. Vérifiez-le puis mettez à niveau.

0
Jin Thakur