Hi. We have a complex product consisting of some dozen solutions. Each solution has a dev environment where it is in unmanaged state. All solutions are hosted in the Azure cloud. DevOps pipelines automatically build and deploy the solutions as managed solutions. Should be a common setup. We have many plugins and all of them write information about the plugin context, parent contexts, shared variables and the like to the trace log. Very valuable information for troubleshooting.
Tracing works perfectly in our development environments. We noticed though, that it does not work when a plugin is part of a managed solution. Currently, it's not clear if it doesn't work for all or only particular plugins. There are no active layers. The plugin I’m investigating is registered correctly, and I have verified that it is executed. I can even use the plugin profiler of the plugin registration tool to capture the execution context. But all ITracingService.Trace calls seem to be entirely ignored, when the plugin is part of a managed solution.
I have spent some time googling around but haven't found anything related. The closest was a reference to CRM 2016 and the requirement to run plugins in sandbox mode. But as stated, it’s all on Microsoft servers and we also use sandboxed mode. Any ideas what else to check?
Thanks in advance.
11
Share
Report
All responses (
Answers (
