AutoMapper VS WexFlow

AutoMapper

The 13.0 Upgrade Guide page was created back in April, but there is no sign of the release yet.

The most well-know is probably AutoMapper, but it's not universally liked.

AutoMapper - well for automapping

When working with AutoMapper, we often bump into runtime errors due to invalid mapping configuration, such as this one:

What problems will resolve automapper?

If you are a fan of data mappers, you might want to enhance the implementation with additional extension methods. Here is an example for AutoMapper.

I'm wondering myself. Most mappers like https://automapper.org/ will make a best effort mapper automatically via introspection. If this is just a DSL/annotation suite that requires explicit, complete mapping implementations then this strikes me as a re-implementation of parts of kotlin in kotlin.

All you need to know are workflow activities which are documented in the wiki. For each activity, you can find a sample workflow available in the backend.

Temporal let you write code as workflows whereas Wexflow let you build workflows with built-in activities without writing any code. You can also create your own custom activities in Wexflow in C#.