We have many custom solutions that use a component that has a dependency on Newtonsoft JSON 11. The site is set up as custom but has /Admin point to a shared Admin folder. Whenever I log in to the backend, Dynamicweb does an upgrade check and then downgrades Newtonsoft to version 8 that ships with the core product leading to a broken site. How can I prevent that from happening? I see a few options:
1. On my server, I just overwrite the DLL in the source's application folder. Works, but requires us to do this every time we update a solution to a newer DW version.
2. Use a custom Admin folder. Works, but adds a lot of disk and management overhead to have custom, isolated versions of the app.
3. Don't overwrite the DLL when it's either not native (i.e. not a Dynamicweb DLL), or b) when the target version is already higher or c) when the target version is registered as a dependentAssembly in web.config.
I'm having fun all day with #1 and #2. Any chance you would want to look into supporting #3?