Beginning in February 2020, AppDynamics switched from Semantic Versioning to Calendar Versioning for some agents and the first deployments of SaaS Controllers. In March 2020, the entire product suite will use Calendar Versioning.


Skip to end of metadata
Go to start of metadata

If the application you want to monitor is executed on Windows, install the AppDynamics .NET Core microservices agent for Windows to your project. Then, set the environment variables described below for your Controller.

Before you Start

Before you install the .NET Core microservices agent, make sure you have access to the AppDynamics Controller where your application metrics will appear.

Install the .NET Core Microservices Agent

  1. Install the AppDynamics.Agent.Windows NuGet package in your project. See your IDE documentation.

    When you install the NuGet package, the AppDynamicsConfig.json file is copied to the project's root directory. A link file prefixed with the project name is included as content to the project. All the files are copied to the app's output directory after the build. 

  2. Set up the following environment variables for your system application:

    CORECLR_ENABLE_PROFILING=1
    CORECLR_PROFILER={39AEABC1-56A5-405F-B8E7-C3668490DB4A}
    CORECLR_PROFILER_PATH_32=<actual_path>\AppDynamics.Profiler_x86.dll
    CORECLR_PROFILER_PATH_64=<actual_path>\AppDynamics.Profiler_x64.dll

    Where <actual_path> is the complete path to the AppDynamics.Profiler dll.

  3. Open the AppDynamicsConfig.json file and update the file with your AppDynamics Controller information.
  4. You have the following options to configure the .NET Agent to connect to the AppDynamics Controller:

    • During development: As shown in the previous screenshot, you can enter your environment variables in the AppDynamicsConfig.json file, and save it in source control.
    • During build: Define your msbuild parameters or environment variables that are passed to the AppDynamicsConfig.json file at build time. The AppDynamicsConfig.json file does not exist at build time, so if you are defining your msbuild parameters or environment variables at build time, you will need to ignore it in source control so that the new AppDynamicsConfig.json file can be created.
    • During runtime: Enter your environment variables in Azure.
  5. Deploy the application.
  • No labels