Mapster.Tool TwoWays Configuration doesn't work
See original GitHub issueMapster.Tool works with ‘AdaptTwoWays’ attribute, but it could be nice to describe Configuration for tool as well, specially for the EF objects.
Mapster.Tool TwoWays Configuration doesn’t work currently:
TypeAdapterConfig<Staff, StaffDto>
.NewConfig()
.TwoWays();
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5
Top Results From Across the Web
Mapster.Tool TwoWays Configuration doesn't work
Tool works with 'AdaptTwoWays' attribute, but it could be nice to describe Configuration for tool as well, specially for the EF objects. Mapster...
Read more >ProjectToType doesn't work with DI(MapContext) · Issue #266
I have this Config public void Register(TypeAdapterConfig config) { config ... I use this way to solve it ... Mapster.Tool and DI #519....
Read more >c# - Mapster not mapping
Step 1 - Create the configuration via implementing IRegister public class BlacklistMapper : IRegister { void Register(TypeAdapterConfig ...
Read more >Mapster, the best .NET mapper that you are (probably) not using
It's a mapping library that it is packing some really amazing features ... Give Mapster a star: https://github.com/MapsterMapper/ Mapster ...
Read more >Getting Started With Mapster in ASP.NET Core
The two-way mapping in Mapster is a simple way to configure ... <Exec WorkingDirectory="$(ProjectDir)" Command="dotnet tool restore" />.
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

I added config to do fluent configuration. Please check https://github.com/MapsterMapper/Mapster/blob/master/src/Sample.CodeGen/MappingRegister.cs
Thanks a lot for details, I see that Interface does not generate extension methods, so it could not be used to keep EF model untouched and have the same mapping as ~config.NewConfig<Staff, StaffDto>().TwoWays(); Hope it will be possible once.