Up to the latest version 4.3 I used Hangfire + Hangfire.CompositeC1 for performing scheduled background jobs. I had Newtonsoft.Json referenced as Nuget-Package with version 7.0.1 and had my C1 package copying THAT Newtonsoft.Json.dll into C1 Bin folder. Web.config was updated accordingly with assembly binding redirect to 7.0.0.0. Everything worked fine.
Now for testing purpose I made a separate new installation of C1 with version 5.0. I installed my C1 packages there without any problems. But when I add scheduled tasks to my web.config (I took some code similar to the Hangfire-C1 example project) and reload the whole page, I get the common error message stating that the Newtonsoft.Json assembly in Version 4.5.0.0 could not be loaded. The same error I get if I (even with no scheduled tasks configured) open the backend and try to load the hangfire dashboard. The page that gets displayed after clicking the respective node in C1 backend displays propertly. But once I click on the hangfire brand link (pointing to root "/hangfire/"), the same assembly error message is displayed (now inside the iframe created by C1).
I also tried to update my own C1 package with the newest nuget packages - without any changes in the above mentioned problems
Now for testing purpose I made a separate new installation of C1 with version 5.0. I installed my C1 packages there without any problems. But when I add scheduled tasks to my web.config (I took some code similar to the Hangfire-C1 example project) and reload the whole page, I get the common error message stating that the Newtonsoft.Json assembly in Version 4.5.0.0 could not be loaded. The same error I get if I (even with no scheduled tasks configured) open the backend and try to load the hangfire dashboard. The page that gets displayed after clicking the respective node in C1 backend displays propertly. But once I click on the hangfire brand link (pointing to root "/hangfire/"), the same assembly error message is displayed (now inside the iframe created by C1).
I also tried to update my own C1 package with the newest nuget packages - without any changes in the above mentioned problems