The Contrast agent is designed to require little to no interaction from the user to set up instrumentation on a .NET Core application. Once the environment is set up through environment variables or application launch profile, the .NET Core agent automatically instruments the ASP.NET Core application. The agent performs analysis as users (or automated scripts or tests) exercise applications. You can view the results of the agent's analysis in the Contrast UI.
The Contrast .NET Core agent consists of two components that run within the same process as your application.
The .NET Profiler that instruments applications to weave in method calls out to agent sensors.
Sensors that gather security, architecture and library information.
These components are located in several DLL files that you may download from the Contrast UI. You can place them anywhere on disk (and they don't need to be placed in your application folder).
To update the agent, replace the agent files in the agent directory and restart your application. As the agent is running alongside your application, it can't update itself.
The agent automatically starts with your application as long as the environment is setup as described in .NET Core installation.
To stop the agent, stop the application and remove agent from its environment. Alternatively, you may change the
CORECLR_ENABLE_PROFILING setting to
Use the Contrast .NET Core agent to analyze ASP.NET applications running on Azure Virtual Machines (VMs), Cloud Services, Mobile Services or Azure App Service (formerly Azure Web Sites). Follow the instructions below to set up the .NET Core agent in your environment.
Installation with Azure Virtual Machines is the same as installation for self-hosted applications. See the .NET Core article on agent Installation for more information.
Installation with Azure Cloud Services or Mobile Services is the same as installation for self-hosted applications. See the .NET Core article on agent Installation for more information.
For information about the installation process with Azure App Service, see the .NET Core article on Express Installation for Azure App Service.