Marek Linka

Looking into the code, the `MinuteInterval` just does `$"*/{interval} * * * *"`: https://github.com/HangfireIO/Hangfire/blob/9cd09f38fa97e4c2dd48f6097985fd2b48b4568e/src/Hangfire.Core/Cron.cs#L231 Therefore `Cron.MinuteInterval(int.Parse(jobScheduler.Duration));` should be equivalent to `$"*/{jobScheduler.Duration} * * * *"`

Well, it's just [cron](https://en.wikipedia.org/wiki/Cron) expressions. While I agree they are not very readable to anyone who doesn't work with Linux regularly, there are some tools to help with them. E.g....

You might notice I'm not involved with this repository/library in any capacity. Found this issue a while back, wanted to share a workaround. You will need to wait for the...

Same issue on the current versions of VSCode (1.43), .NET Core SDK (3.1.102), and the extension (0.7.1). I have pretty much the same output - the test process finishes, the...

To be honest, in the meantime I forked the code and did some changes and improvements to it, currently running that version. I might give the official version a spin...

I was originally thinking exactly that but it looked like the project might be inactive at the time. I'll definitely give it a look to see what could be useful....

I just started encountering this same after installing the newly-released C# Dev Kit for VSCode. It seems the processes started by VSCode keep a handle open on the assemblies: ```...

@stefanforsberg Here's the screenshots. Sorry about the weird color tone, I'm on an HDR display the screenshot utility is not handling that particularly well. 1. Nested classes:  Navigation to...