AutoMapper: System.ValueTuple package should not be referenced for .NET 4.7+ projects
Version: 7.0.1
Expected behavior
System.ValueTuple dependency should not be included in projects that target .NET 4.7 and up.
Actual behavior
System.ValueTuple dependency is added and causes our web projects, which target .net 4.7.2, to require the following web.config binding redirect:
<dependentAssembly>
<assemblyIdentity name="System.ValueTuple" publicKeyToken="CC7B13FFCD2DDD51" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-4.0.3.0" newVersion="4.0.3.0"/>
</dependentAssembly>
Which is in turn leading to a System.ExecutionEngine
exception for us in w3wp.exe that I’ve been unable to track down. Our projects are a mix of .NET 4.7.2 and .NET Standard 2.0 projects and the dependency is likely causing a binary compatibility issue between the different implementations. We’ve experienced similar issues with System.Net.Http in the past.
With AutoMapper 7.0.0, the dependency is not there, and all works well.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 27 (14 by maintainers)
Commits related to this issue
- Dropping value tuples. Fixes #2750 — committed to AutoMapper/AutoMapper by jbogard 5 years ago
- Dropping value tuples. Fixes #2750 — committed to AutoMapper/AutoMapper by jbogard 5 years ago
- Dropping value tuples. Fixes #2750 — committed to AutoMapper/AutoMapper by jbogard 5 years ago
- Update - Waaay behind (#1) * not needed * cycle * reverse include members * reverse to included members * cosmetic * cosmetic * xml docs * before/after map * ForPath * cosm... — committed to madmonkey/AutoMapper by madmonkey 5 years ago
I’m also experiencing troubles with
System.ValueTuple
versions conflict when referencing AutoMapper v8.0.0 package in net472-targeted projects.I’ve got the following weird build warning:
There were no such problems with AutoMapper v7.0.0 package.
Just curious, what the overhead for you will bring adding an extra net47 build target to AutoMapper?
I think dropping net461 build target will work for me also 😃
Yep!
On Wed, Apr 24, 2019 at 9:45 AM SkinnySackboy notifications@github.com wrote:
I think with the last PR we’re ready. Next day or so?
On Wed, Apr 17, 2019 at 12:03 PM SkinnySackboy notifications@github.com wrote:
Ha no I have many clients still on 4.6
On Wed, Feb 20, 2019 at 10:48 AM Lucian Bargaoanu notifications@github.com wrote: