Build Output: Consider app.config remapping of Assembly

Question

Build Output: Consider app.config remapping of Assembly

Asked 9 years, 2 months ago

Viewed 525 times

2

I am receiving the message below regarding several Assemblies, the project compiles and runs normally, however, wanted to know how to solve and whether it can cause future problems.

Consider app.config remapping of Assembly "System.Net.Primitives, Culture=neutral, Publickeytoken=b03f5f7f11d50a3a" from Version "3.9.0.0" [] to Version "4.0.0.0" [C: Program Files (x86) Reference Assemblies Microsoft Framework Monoandroid v1.0 Facades System.Net.Primitives.dll] to Solve Conflict and get Rid of Warning.

I don’t know but this may help you: https://msdn.microsoft.com/en-us/library/7wd6ex19(v=vs.110). aspx

– Maniero

2015/08/26 at 16:15
I’ll read it carefully to see if it solves this problem, thank you.

– rubStackOverflow

2015/08/26 at 18:39
It’s an old question but I must ask, have you managed to remove these warnings?

– stderr

2015/09/12 at 22:47
They only disappeared after the component was updated. I couldn’t figure out the cause or how else to solve it.

– rubStackOverflow

2015/09/12 at 23:05

1 answer

Browser other questions tagged visual-studio-2013 visual-studio compilation

You are not signed in. Login or sign up in order to post.

by Leonel Sanches da Silva • **88,623** points · Answer 1 · 2015-09-13T06:42:16+00:00

This section is in the web.config:

<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      ...
      <dependentAssembly>
        <assemblyIdentity name="System.Net.Primitives" culture="neutral" publicKeyToken="b03f5f7f11d50a3a" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
      </dependentAssembly>
      ...
    </assemblyBinding>
    ...
  </runtime>
  ...
</configuration>

Basically, you indicate a range of versions in oldVersion and the Assembly most recent in newVersion. It’s not much of a secret.

The compiler gives this warning when the version of Assembly was found, but this may not always happen. The above setting solves this problem.