Home/ Questions/Q 3426552
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T06:43:47+00:00

In my application there is a loader executable (let’s call it Loader.exe). It searches

  • 0

In my application there is a “loader” executable (let’s call it “Loader.exe”). It searches a specific folder for DLL files and loads them one-by-one. Then the user can choose which plugin to run (plugins have windows and business logic). This is a kind of a plugin architecture I have currently implemented.

The problem with that is that none of the run-time explorer tools for WPF and profilers can see what is happening inside the loaded DLLs. E.g. the CLR Profiler does not gather any data at all.

Is there anything I could do to fix this without rewriting the DLL loading part of the project? And, frankly, why don’t those profilers see the loaded DLL code? VS debugging works great in those.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Try my profiler http://www.xteprofiler.com , if it doesn’t work, I will fix it so it does.

    • 0