.net core web api controller life cycle

Question

hello I understand the life cycle of injected service like scoped that after the request is finished the service is unavailable. But the parameter (like myObject in the example) when their are destroyed? If i pass this parameter to long async task and I don't await the result I could have some problem of null in the task?

public class mycontroller : ControllerBase
{
    private MyService _myservice;

    public mycontroller(MyService myservice)
    {
        _myservice = myservice;
    }

    [HttpPost]
    public IActionResult Post([FromBody] MyObject myObject)
    {
        _myservice.dosomethinglongasync(myObject);
        return OK();
    }
}

Normal .net object life cycle rules apply. Instances are GCed once there are no more references. As far as how to do a fire/forget in asp.net core there are other already asked and answered questions about that on Stack Overflow. — Igor
– Igor, Commented May 10, 2021 at 15:20

johannespartin · Accepted Answer · 2021-05-10 16:32:54Z

1

The task will continue to hold a reference onto myObject until it's completed. You should not face an issue that it's destroyed beforehand.

But(!) this is a bad design. You can not check the task for completion, etc. Firing async tasks without awaiting them somewhere is no good practice.

answered May 10, 2021 at 16:32

johannespartin

5113 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

.net core web api controller life cycle

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related