.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.
To profile a .NET Core application, you should specify the following parameters:
Full path to the executable (.exe) or library (.dll) file of the profiled application.
If Advanced is selected, you are able to additionally specify the following parameters:
Optional arguments passed to the executable of the profiled application.
Full path to a custom working directory of the profiled application.
Profile child processes
If selected, dotMemory will profile not only the main app process but the processes it runs as well. Note that you can profile only specific child processes. Learn how to do this next in this section.
Use environment variables
Enables you to run the profiled application with specific environment variables. You can specify any number of variables using the list below the option. Note that each variable must be specified on a new line.
URL to invoke the web application.
A browser that should run the application. The default system browser is pre-selected.
Filtering Child Processes
If you want to profile only specific child processes, you can set up a process filter. The filter is a semicolon-separated list of process names that must not be profiled.
To use a process filter
Select Profile child processes.
In Excluding, add process name masks separated by semicolon (;).
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".
*wildcard is supported.
For example, if you add the
service* mask, all processes which name starts with
service will be ignored by the profiler.