Skip to content

Building an Asp.Net Core application targeting desktop framework generates binding redirect warnings #315

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
BillHiebert opened this issue Oct 24, 2016 · 0 comments
Assignees
Labels
Milestone

Comments

@BillHiebert
Copy link
Contributor

Create a new ASP.NET core web application targeting DotNet 4.5.2. After restoring the build generates the following warnings. Should these warnings be disabled for this scenario? Or if they are valid, should the targets file be updated to automatically apply these binding redirects?

1>Consider app.config remapping of assembly "Newtonsoft.Json, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed" from Version "6.0.0.0" [] to Version "9.0.0.0" [C:\Users\billhie.nuget\packages\newtonsoft.json\9.0.1\lib\net45\Newtonsoft.Json.dll] to solve conflict and get rid of warning.
1>Consider app.config remapping of assembly "System.Collections.Immutable, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "1.1.37.0" [] to Version "1.2.0.0" [C:\Users\billhie.nuget\packages\system.collections.immutable\1.2.0\lib\portable-net45+win8+wp8+wpa81\System.Collections.Immutable.dll] to solve conflict and get rid of warning.
1>Consider app.config remapping of assembly "Microsoft.AspNetCore.Routing.Abstractions, Culture=neutral, PublicKeyToken=adb9793829ddae60" from Version "1.0.0.0" [] to Version "1.0.1.0" [C:\Users\billhie.nuget\packages\microsoft.aspnetcore.routing.abstractions\1.0.1\lib\net451\Microsoft.AspNetCore.Routing.Abstractions.dll] to solve conflict and get rid of warning.
1>Consider app.config remapping of assembly "Microsoft.AspNetCore.Routing, Culture=neutral, PublicKeyToken=adb9793829ddae60" from Version "1.0.0.0" [] to Version "1.0.1.0" [C:\Users\billhie.nuget\packages\microsoft.aspnetcore.routing\1.0.1\lib\net451\Microsoft.AspNetCore.Routing.dll] to solve conflict and get rid of warning.
1>Consider app.config remapping of assembly "System.Reflection.Metadata, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" from Version "1.2.0.0" [] to Version "1.3.0.0" [C:\Users\billhie.nuget\packages\system.reflection.metadata\1.3.0\lib\portable-net45+win8\System.Reflection.Metadata.dll] to solve conflict and get rid of warning.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1900,5): warning MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190.
1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Microsoft.Common.CurrentVersion.targets(1900,5): warning MSB3270: There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "C:\Users\billhie.nuget\packages\microsoft.aspnetcore.razor.tools\1.0.0-preview2-final\lib\net451\dotnet-razor-tooling.exe", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
1>WebApplication3 -> C:\Users\billhie\documents\visual studio 2017\Projects\WebApplication3\src\WebApplication3\bin\Debug\net452\WebApplication3.exe

@srivatsn srivatsn added the Bug label Oct 24, 2016
@srivatsn srivatsn added this to the 1.0 Preview milestone Oct 24, 2016
@srivatsn srivatsn assigned nguerrera and dsplaisted and unassigned nguerrera Oct 24, 2016
sbomer pushed a commit to sbomer/sdk that referenced this issue Sep 19, 2017
mmitche pushed a commit to mmitche/sdk that referenced this issue Jun 5, 2020
Fix the build for release/2.1 branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants