Before you start

To profile a COM+ server application correctly, set the ApplicationActivation attribute as follows:

[assembly: ApplicationActivation(ActivationOption.Server)]

If you cannot set this attribute (for example, if you do not have access to the source code), or if you set it to ActivationOption.Library, you may still be able to profile the COM+ application by profiling the client application. You should note, however, that the resulting server application:

• will not be a true COM+ application and will run in the client process
• will be treated by ANTS Memory Profiler as a DLL invoked by the client.

Also, you may need to make the application's code fully trusted by setting the ApplicationAccessControl attribute as follows:

[assembly: ApplicationAccessControl(false)]

Profiler settings

1. Start ANTS Memory Profiler. If it is already running, on the File menu, click New Profiling Session...
2. On the ANTS Memory Profiler Settings dialog box, on the Application Settings tab, select COM+ Server.
3. Next to COM+ server application choose the COM+ server application from the dropdown list. Click the  icon to refresh the list, for example, if you have started the server since the ANTS Memory Profiler Settings dialog box was displayed.
4. You should normally leave Profile child processes and Monitor disposal of objects selected, although monitoring the disposal of objects may impact the performance of your application.
5. Under Client application, next to Executable, choose the path to the client application.
6. If required, specify any Arguments required by the client application.
7. If required, change the performance counters to record.
8. Click .
9. Use the client application to test the COM+ server application during your profiling session.
10. Check whether there are any memory problems.