# Netcore Always Start still relivant?

**URL:** <https://discuss.hangfire.io/t/netcore-always-start-still-relivant/3675>\
**Category:** question\
**Tags:** long-running\
**Created:** [August 7, 2017, 8:54pm UTC](https://discuss.hangfire.io/t/netcore-always-start-still-relivant/3675 "2017-08-07T20:54:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![OOD](https://avatars.discourse-cdn.com/v4/letter/o/a6a055/32.png) [@OOD](https://discuss.hangfire.io/u/OOD)\
**Post date:** [August 7, 2017, 8:54pm UTC](https://discuss.hangfire.io/t/netcore-always-start-still-relivant/3675/1 "2017-08-07T20:54:27Z")

</div>

Hi All,

I’m looking at using this for our scheduling needs. One question though; Is the following link still required if used in .netcore mvc?

[http://docs.hangfire.io/en/latest/deployment-to-production/making-aspnet-app-always-running.html](http://docs.hangfire.io/en/latest/deployment-to-production/making-aspnet-app-always-running.html)

We’re planning on running this Linux containers, so I’m unsure how I’d go about setting that? I assume its always netcore apps are started by a console app?

Thanks!

---

<div class="post-metadata">

**Author:** ![pieceofsummer](https://dub1.discourse-cdn.com/flex017/user_avatar/discuss.hangfire.io/pieceofsummer/32/785_2.png) [@pieceofsummer](https://discuss.hangfire.io/u/pieceofsummer)\
**Post date:** [August 7, 2017, 10:16pm UTC](https://discuss.hangfire.io/t/netcore-always-start-still-relivant/3675/2 "2017-08-07T22:16:41Z")

</div>

No, the link above is only for IIS-hosted applications.

.Net Core applications always run as a separate process, and won’t be stopped/restarted because of quotas or timeouts. You just need to correctly configure `systemd` (or whatever) to run your application on startup.