question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

New update doesn't work with AutoMapper.

See original GitHub issue

I just updated SteamWebAPI2 to v2.0.0.33 and now it gives me an error whenever I run new SteamUser.

Here’s the error:

Managed Debugging Assistant 'BindingFailure' has detected a problem in '[path]

Additional information: The assembly with display name 'AutoMapper' failed to load in the 'LoadFrom' binding context of the AppDomain with ID 1. The cause of the failure was: System.IO.FileLoadException: Could not load file or assembly 'AutoMapper, Version=4.2.1.0, Culture=neutral, PublicKeyToken=be96cd2c38ef1005' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

And this shows up in my warning list: Found conflicts between different versions of the same dependent assembly that could not be resolved. In the file at C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets. (btw when I open that file I get 102 warnings lol).

I also can’t update AutoMapper because SteamWebAPI2 depends on version 4.2.1.

Any help?

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
babelshiftcommented, Nov 26, 2016

Hey dude don’t worry about it. This is just a fun side project for me. Any help that I can provide to people is good for me.

Glad you figured it out.

0reactions
Tvde1commented, Nov 26, 2016

Yes it was an error in my App.config.

If anyone else might ever get this problem, remove

  <dependentAssembly>
    <assemblyIdentity name="AutoMapper" publicKeyToken="be96cd2c38ef1005" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-5.2.0.0" newVersion="5.2.0.0" />
  </dependentAssembly>

From App.config.

Sorry to bother you with this. I know this isn’t what issues are for.

Read more comments on GitHub >

github_iconTop Results From Across the Web

c# - AutoMapper does not update Collection items
1 Answer 1 ... I found the problem. I added this to map the collections to the AutoMapper configuration: cfg.CreateMap<IReadOnlyList<Item>, List< ...
Read more >
11.0 Upgrade Guide
11.0 Upgrade Guide¶. Release notes. AutoMapper now targets .Net Standard 2.1 and doesn't work on .Net Framework ...
Read more >
Automapper - Update object ORM
am trying to update an object using telerik openaccess orm and automapper, it works for adding the object to scope but not update....
Read more >
The reasons behind why I don't use AutoMapper.
I've encountered cases when AutoMapper transforms simple thing like mapping values from object to other into a really complex problem, which ...
Read more >
I hate AutoMapper : r/dotnet
When I left that job someone was 6 months into a project to fix all the mappings so they worked on the latest...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found