You mentioned that you got error after you deployed it to the server. Does it work on your local computer?

My tests cases of the Job, running inside of VS 2019 work fine. When Quartz.Net executes the job on the server, while referencing RingCentral, I get the errors. I don't know if RingCentral is causing a binding redirect, but both issues only seem to arise, when one or both project reference RingCentral.

Clarification.

It is a Windows console app that uses TopShelf to run as a Windows service. It uses Quartz.Net to run scheduled jobs. I only get the above errors, when the desired job executes.

Does this video help? https://www.youtube.com/watch?v=SRQzxqw1bm0

I have no experience with Quartz.Net. Have you contacted its support?

@Tyler Liu The video just shows adding the Nuget package. I don't have a problem there. I don't know that TopShelf or Quartz.NET have anything to do with it. I'm not sure if they may cause an issue for RingCentral. I can deploy the scheduling app, without RingCentral, and have no problem. It is only when I add the RingCentral package that I get what appears to be issues with binding redirects. It is just very odd that the scheduling program runs OK. The RingCentral test case runs OK. It is only when I add RingCentral to the scheduling program that there is an issue.

Idea: since both RingCentral and Quartz support .Net Core. Can you make the scheduling program target .Net Core instead of .NET framework 4.6.2 ?

@Tyler Liu because it is a Windows service, it would have to be .NET Core 3, which supports desktop applications. At one point, I tried to convert it to .NET Core 3 and deployed the runtime (which is still in Beta) to the server. However, I have not been able to get it to run on the server. Thus, I went back to .NET Framework.