Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
04-09-2018 11:27 PM
We were upgrading our project to .Net 4.6.2 and we came across an issue where we used to get the exception. "Cannot load file or assembly System.Net.Http..." intermittently because the appD profiler was interfering in the order of loading assemblies. The appD team asked us to put the line
Solved! Go to Solution.
04-12-2018 03:11 AM
04-12-2018 03:14 AM - edited 04-12-2018 03:18 AM
Thank you for the answer. I understand that this tag controls the behaviour of the profiler with regards to dynamically loaded assemblies. May I also know what happens when you set <full-no-dependency-mode enabled /> to True and when you set it to false?
04-12-2018 03:19 AM
Hi,
Sorry this is what I explained in first two line
full-no-dependency-mode : This config is specific to .Net Profiler which helps it to identify what modules are loaded in the process. This also helps detect dynamically loaded assemblies and how the agent is instrumenting them. This is extremely internal to .Net CLR Profiler implementation
Thanks,
Raunak
04-12-2018 03:24 AM
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form