Setting up the session

1. On the startup page, click New profiling session.
2. Under Cloud & serverless, select Azure Functions (Core Tools).
3. In Working Directory (Azure App), select your function project folder.
4. Check Path to Azure Functions Core Tools (func.exe).
   ANTS Memory Profiler normally fills this in automatically. It first looks for a cached Core Tools build that matches your project type,
   isolated or in-process. If no matching cached build is available, it searches PATH, standard npm installation locations, and the standalone Core Tools installation directories.
   To use a different Core Tools installation, click ... and browse to func.exe.
5. Optionally, click Show startup options and change Command line arguments. The default is start.
   For example, use start --port 7072 if port 7071 is already in use.
6. Choose any other options, then click Start profiling.

What happens when you start profiling

1. Your function project is built (dotnet build). The build isn't profiled.
2. func.exe starts your function app and the profiler attaches to it. Child processes are always profiled, because your function code runs in a process started by func.exe.
3. When the host is ready, call your functions as normal. For example, for an HTTP trigger, open http://localhost:7071/api/<FunctionName> in a browser.
4. Take memory snapshots as usual.
5. When you've finished, click Stop profiling. func.exe and the worker process are stopped.

Finding your objects in a snapshot

For isolated function apps, your code runs in a separate worker process (dotnet.exe) started by func.exe. In the class list, select that dotnet.exe in the Process list to see your objects.

If profiling doesn't start