The procedure for profiling XBAP applications depends on whether your application is locally or remotely-hosted.

To profile a locally-hosted XBAP application

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 XBAP (local XAML browser application).
3. Enter the path to the XBAP application that you want to profile.
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. If required, change the performance counters to record.
6. Click .
7. Check whether there are any memory problems.

To profile a remote XBAP application

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 .NET executable.
3. Enter the path to Microsoft Internet Explorer (iexplore.exe).
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. If required by your application, specify its Working directory. By default, the directory containing the .NET executable is used.
6. If required by your application, specify any Arguments which should be supplied to the .NET executable at launch.
7. If required, change the performance counters to record.
8. Click .
9. When Internet Explorer starts, navigate to the XBAP application and interact with it in the normal way.
10. Check whether there are any memory problems.