You cannot include a type map into itself error

[NCC1701M]

Source/destination types

There are no information about which types are involed

Mapping configuration

Always using CreateMap<Model, ViewModel>() and ReverseMap

Version: 11.0.0

Expected behavior

No error!

Actual behavior

After upgrading from AutoMapper 10 to 11 it raises the error:
You cannot include a type map into itself error

What does this error mean? Where and why does it happen? All mappings worked perfectly with AutoMapper version 10 and AutoMapper.Extensions.Microsoft.DependencyInjection version 8.1.1 and now this error.

There needs to be a documentation about this error or at least in the exception should be the name of the effected class.

[lbargaoanu]

A repro would help. Make a gist that we can execute and see fail.
For the error message, a PR is welcome.

[NCC1701M]

The symbol packages are published so you should be able to debug with anything that supports symbol packages - Rider etc. You don't need the source code to debug.

I'm using VSCode, don't know if OmniSharp supports this. Also couldn't find any symbol files for AutoMapper in my bin or obj folders. Right now I can't step into for example CreateMap

[jbogard]

No it does not because Microsoft closed-source its debugger to force people to use Visual Studio (or VS Mac).

Your best bet is to use an IDE that has a full-featured debugger

[NCC1701M]

Sorry, can't do. We're using VSCode.

[jbogard]

Then you're out of luck 🤷‍♂️

[jbogard]

One other thing you can try to debug locally is to pull down the code and reference ONLY the .csproj in your application (removing nuget package references).

Otherwise the problems you have debugging are of entirely using VS Code instead of an actual IDE. I can't help you if you can't use the right tool for the job.

[jbogard]

You can download a full IDE as a trial. Rider or VS Mac work great. The Omnisharp extension will always be intentionally under-developed by MS.

…

On Jan 10, 2022, at 9:06 AM, NCC1701M ***@***.***> wrote:  Then you're out of luck 🤷‍♂️ It seems so. But I'm afraid you can't assume everyone can debug your library. Which makes the last answer of the your "colleague" sound pretty harsh and on the edge. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.