DynamicProxy | Natasha-based dynamic proxy

This will help you to find your way;

It seems to me you are trying to utilize the benefits of dependency injection, which is good. However, at the moment you are using BaseRepository as the dependency rather than IBaseRepository which makes IBaseRepository kinda redundant and couples your classes tightly to a specific implementation (BaseRepository). This also means that you have a hard dependency on DatabaseContext because that's required to instatiate a BaseRepository. If you go back one step and utilize IBaseRepository for a more loose coupling you will at the same time avoid the dependency on DatabaseContext and thus make unit testing easier as well.

First, change the definition of your ServiceBase:

I'm not sure what do you mean by stateless class - do you mean that it doesn't have any fields? what is a stateless class?

Base implementation in your example is as good as not overriding at all. You need to ask yourself a question:

What makes two objects of type MiHook equal?

Judging by your implementation of ShouldInterceptMethod it is the Type(IFoo.Bar). If that's the case, I would go for a IFoo.Bar - "dependent" override:

I figured it out in the end... I had to give the Mock a parameter(null) when creating it like this:

I solved the problem using UseInterceptorAttribute in the interface methods. Because the interceptor is enabling for interface:

For the sake of anyone else landing on this from google...

We are using the latest Rider/ReSharper EAP (2020.2 EAP 8) which has introduced this bug when:

• Running tests via the Rider/ReSharper test runner
• The test project references and uses a mocking library that attempts to generate dynamic proxies (Moq, NSubstitute, etc...)

This has been fixed by JetBrains in their development branch and will be fixed in the next EAP. You can track this here: https://youtrack.jetbrains.com/issue/RIDER-48134

Update: EAP 9 is out which fixes this 🎉 You can use JetBrains Toolbox to update.

After trying everything, I circled back to nHibernate 5.X change logs, ended up here: https://nhibernate.info/doc/nhibernate-reference/transactions.html, and found this little note at the very end of the changelog:

As of NHibernate v5.0, FlushMode.Commit requires the configuration setting transaction.use_connection_on_system_prepare to be true for flushing from transaction scope commit. Otherwise, it will be your responsibility to flush the session before completing the scope.

Using transaction.use_connection_on_system_prepare can cause undesired transaction promotions to distributed: it requires using a dedicated connection for flushing, and it delays session disposal (if done inside the scope) to the scope disposal. If you want to avoid this, set this setting to false and manually flush your sessions.

For new applications, it is recommended to set transaction.use_connection_on_system_prepare to false, and to flush explicitly your sessions before scope completion. For old applications, consider checking how sessions are flushed, and if possible switch it to false too.

Basically, the one setting we had changed while migrating to nHibernate 5 was the FlushMode from "Auto" to "Commit", but somehow missed this flag (transaction.use_connection_on_system_prepare = false).

Hope this will help other people with legacy systems trying to upgrade!

It's all about registration order. There's a section in the documentation on it.

Basically: Last in wins.

First, it's important to note that what you're using in your example is the Microsoft.Extensions.DependencyInjection library. None of that is Autofac. Autofac can integrate with that, but the way you're setting up your registrations using IServiceCollection is not Autofac.

However, the concept last in wins holds for Microsoft DI as well as Autofac... and almost every other DI container.

If I register three things that implement the same interface...

I think you should've shared the endpoint goal of it, because the thing you are asking for is very alien for AS3 concepts.

Still, it is, with certain limitations, doable.

Implementation: