.NET Core Applications
.NET Core applications include Windows applications based on .NET Core: self-contained application deployments that have a .exe executable file or framework-dependent deployments that have only a .dll file.
In order to profile a standalone application, you should specify the following parameters:
Full path to the executable (.exe) or library (.dll) file of the profiled application.
If the Advanced checkbox is turned on, you are able to additionally specify the following parameters:
Optional arguments passed to the executable of the profiled application.
- Working directory
Full path to a custom working directory of the profiled application.
- Profile child processes
If checked, dotMemory will profile not only the main app process but the processes it runs as well. Note that you can set up dotMemory to profile only specific child processes. Learn how to do this next in this section.
Filtering Child Processes
If you want to profile only specific child processes, you can set up a process filter. In this case, dotMemory will start profiling of a child process only if its name matches the filter.
The filter consists from an arbitrary number of name masks for the processes that should not be profiled.
To use a process filter:
- Click the Filter Processes button.
- In the opened dialog, add masks by using the text field and the Add button.
- To save the filter, click Save.
Take into account the following filter peculiarities:
- The default policy is "profile all".
- There can be only "exclude" masks. Therefore, any filter mask you add means "do not profile anything that matches this mask".
- The asterisk
*wildcard is supported.
For example, if you add the
service* mask, all processes which name starts with
service will be ignored by the profiler.