structuremap | A Dependency Injection/Inversion of Control tool for .NET | Dependency Injection library

StructureMap by design will always build a fresh instance if you pass custom constructor parameters via ExplicitArguments. You might want to use named instances instead like this:

Your general logic is flawed. You expect things to run, even after your http call is already over.

Once you return a response, things happen in the ASP.NET framework.

Dependency injection containers finish their scope, objects get disposed.

Keeping those references that are probably scoped or transient in nature until after the call has completed is not going to work. Granted, sometimes it might work, when you have classes that do not implement IDisposable or you just get lucky with a microsocond timing, but generally speaking, this is not anticipated and not meant to work.

If you want to do work after sending out the reply, you have to hand this work over to another party. Maybe you save it into a database and another service picks it up and works on it. Or maybe you have another program or thread running and you try some IPC. But you should not expect threads or tasks referencing things from the scope of your http call to work after it's done.

The lambda expression:

The first thing to do is to check out the type scanning diagnostics:

http://structuremap.github.io/diagnostics/type-scanning/.

The type scanning can be a little brittle if there are missing assemblies. The diagnostics might point out where things are going wrong. Also, try your WhatDoIHave() diagnostics too.

And also, just making sure that you know that StructureMap is no longer supported and has been replaced by Lamar:

• https://jeremydmiller.com/2018/01/29/sunsetting-structuremap/
• https://jasperfx.github.io/lamar

This cant be done. Structuremap doesn't support standard 2.0.. Went back to EF6 and will do the migration to EF core once the MVC is upgraded to core(and stucturemap is not needed in mvc2 anymore)

Something in your Directory.Build.props has core depedencies, such as Castle.Core. Can you load in AspNetCore or drop the .core dependencies?

I used following code to solve the problem:

You didn't specify which MassTransit version you were using, but the recommended way to set this up since MassTransit 6.1 is to use the AddDbContext method in the container integration package (which should be MassTransit.StructureMap in your case). You can see an example here: https://masstransit-project.com/usage/sagas/efcore.html#container-integration.

Snippet from that webpage:

What we can do is introduce another interface for return type and all the types that will be returned will implement it.

Define an interface :