Andreas Ravnestad

Can you explain what you expect to happen here?

Hi @heggi, This might be a long shot, but can you try to inject IMapper? Like this: `builder.Services.AddTransient();` If that doesn't work, could you post a complete code sample please?

Okay, I narrowed it down to MapContext.Current being null. I will investigate some more :)

So I found that MapContext.cs was changed in [a commit](https://github.com/MapsterMapper/Mapster/commit/52fe4e4f45f9a37c66b9374cc6c7d643f26d7685) that fixed issue #266. It seems that AsyncLocal breaks DI with generated code in ASP.NET Core (and possibly other things...

Basically the way Mapster works now we have to choose between two evils -- [ThreadStatic or AsyncLocal](https://github.com/MapsterMapper/Mapster/blob/fb325ef85971ba527bff80cfd70c89a47a7442a8/src/Mapster.Core/MapContext/MapContext.cs#L18). Currently Mapster will use AsyncLocal in .NET 6 and .NET Standard, and ThreadStatic...

Seeing as how much potential there is in LiteDB, especially with the advent of .NET Core in the past few years and now .NET 5 and .NET MAUI. I'd be...

I'm a big fan of this tool and use it on a regular basis. I was flustered to see that it doesn't support specifying query string parameters. I see that...

Hi @SehirBilisim, We made an honest attempt to get the Oracle dialect working properly, but without improved support for user types in the Oracle ODP drivers, this is not possible....

@peetw Now this is a level of ambition I can admire ;) Do you have some ideas on how to move forward with this?

Thank you for this awesome contribution @boylec. If you have some extra time to spare, please update the [Wiki](https://github.com/MapsterMapper/Mapster/wiki) to reflect the new API changes.