I have a project which has several NuGet packages installed. It seems the NuGet package manager automatically generates binding redirects to assemblies, and somehow this is creating a conflict, that ultimately is resolved during the build, but still generates a warning.
I've used the same packages in other projects before, but today after installing, I started getting warnings like this (and several other similar warnings) in the build output:
Severity Code Description Project File Line Suppression State
Warning The explicit binding redirect on "[url removed, login to view], Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" conflicts with an autogenerated binding redirect. Consider removing it from the application configuration file or disabling autogenerated binding redirects. The build will replace it with: "<bindingRedirect oldVersion="0.0.0.0-22.214.171.124" newVersion="126.96.36.199" xmlns="urn:schemas-microsoft-com:[url removed, login to view]" />".
I'm looking for someone who is experienced in resolving this warning to walk me through how to fix it-- maybe by editing the config? I belive everything should run just fine as it is, but I'm not one to leave warnings in my projects.
C# Visual Studio Community 2017
I've attached the App.config which has the binding redirects, I believe.
8 威客就此工作平均出价 $43
I possess vast experience in the areas concerned: design, coding, testing and documentation, analyzing and error correction on existing source code (automating where suitable) using the mentioned tools.