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.
Skoruba.IdentityServer4.Admin.BusinessLogic.Mappers.ClientMappers exception when upgrading from automapper 8.0.0 to 8.1.0
See original GitHub issueHi, my project was generated using beta5. When upgrading from automapper 8.0.0 to 8.1.0, the Clients vieew (Configuration/Clients) stopped working with the following exception:
'Skoruba.IdentityServer4.Admin.BusinessLogic.Mappers.ClientMappers' threw an exception. <--- Exception has been thrown by the target of an invocation. <--- Method not found: 'AutoMapper.IMappingExpression`2<!0,!1> AutoMapper.IMappingExpression`2.ConstructUsing(System.Linq.Expressions.Expression`1<System.Func`2<!0,!1>>)'.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:8 (5 by maintainers)
Top Results From Across the Web
upgrade to ids 2.5 version and automapper 8.1.1 crash #314
ClientMappers' threw an exception. Skoruba.IdentityServer4.Admin.BusinessLogic.Mappers.ClientMappers.ToModel(PagedList clients).
Read more >Method not found: '!!0 AutoMapper.IMapper.Map(System. ...
It seems that the AutoMapper 10.0.0 has a bug, the solution to that problem was to upgrade AutoMapper to 10.1.1 version.
Read more >IdentityServer (SQLite DB) on .NET 7
EntityFramework.Mappers.IdentityResourceMappers' threw an exception.” To resolve this error, update the version of the 'AutoMapper' package ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Version 8.1.1 is out now. Did anybody check to see if the issue was fixed? If not, I’ll try upgrading tomorrow.
Fixed and available in master