bhehe

The question as to "really is static" remains, but I realized there is another 'in memory' storage provider variant with the other one coming from the Hangfire team itself, I...

fwiw, if anyone encounters this later. the same issue exists with the Hangfire-provided version of the in-memory storage provider. When switching to use of a SQL Server local DB for...

Just ran into this myself; Is there a more broadly applicable fix to issues of this nature? Seems like it would be a problem any time there's a version mismatch...

Also note that given the generic naming, I have to consider renaming while copying so as it's clear & obvious what the script is and that it wouldn't have any...

With further research, there's quite a few conversations out there around how to handle package contents and them being emitted/output as part of a build. The "right solutions" all seem...

### New Findings On a hunch, I switched the test code back to using a local SQL database instance instead of the in-memory storage provider. With that change, all the...

I've created a related issue over in the 'InMemory' repo's issues tracker as it's starting to sound like it may be more appropriate to chase it there.

Let me get you some code extracts but also for context, I did try an experiment where I registered all jobs so even in a "1st one wins" scenario they...

So for the 1st question on how we register the jobs; Yes, we do use the static class/method. So if I'm understanding you, I would need to pass in the...

Given your comment about the static state management, what isn't making sense to me is that with my experiment to register all jobs in all tests - why did the...