Using exception tracer with frameworks in DLLs

The previous sections assumed that you write DLLs without using any frameworks. If you use framework (such as VCL or IntraWeb), then your actions will be slightly different. That's because framework already contain some sort of exception handling code.
 
A general concept would be the same. You can use either "Lightweight DLL" or "Standalone DLL" profiles for your DLLs. So the previous facts would be the same. Additionally, you have to configure DLLs for your framework. EurekaLog has support for common cases out of the box. For example, if you use Forms unit in your DLL (i.e. your DLL has forms) - then you need to hook Application.HandleException method. This can be done by enabling "VCL Forms application" option on Advanced/Code/Hooks page in EurekaLog project options. This is true for both "Lightweight DLL" and "Standalone DLL" profiles.
 
Note: "Standalone DLL" profile with "VCL Forms application" option on Hooks page is equal to "VCL Forms Application" profile. When you enable such options - DLL profile will be switched to "VCL Forms Application" profile. This is a normal behavior. After all, a profile is just set of predefined options. If you change options to match another profile - it will be shown as used. There is no build-in profile for "Lightweight DLL" profile with "VCL Forms application" option, so "Lightweight DLL" profile will not be changed after enabling option.
 
Now, let's change our example to illustrate this on practice. As usual, host application will remain unchanged. All changes will be done for DLL.

See also: