1. Home
  2. Language Guides
  3. .NET
  4. APM
  5. Scripted installation

Scripted installation

The current production installers validate release metadata and install the matching Agent, profiler, and managed startup hook. They do not accept an API key because each application owns its own Raygun application key.

Run the latest signed MSI bootstrap from an elevated PowerShell process:

Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1 | Invoke-Expression

Pin an exact version when a deployment requires repeatable bytes:

& ([ScriptBlock]::Create((Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1))) -Version 3.1.3

Repair or restore all files from the already-installed selected version:

& ([ScriptBlock]::Create((Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1))) `
  -Version 3.1.3 -Reinstall

The default installation is silent and does not restart Windows. Add -Interactive to display the MSI user interface.

After installation, configure IIS application pools or supported Windows services with the Configuration Utility or current Agent command line, then restart each application.

Install the latest AMD64 or ARM64 release:

curl -fsSL https://downloads.raygun.com/apm/install.sh | sudo sh

Pin an exact version:

curl -fsSL https://downloads.raygun.com/apm/install.sh \
  | sudo sh -s -- --version 3.1.3

The Linux installer prints the environment required by each application, including DOTNET_STARTUP_HOOKS for automatic ASP.NET Core request correlation. Add the application API key, profiler variables, and startup-hook setting to the application's service definition, then restart that application. See .NET on Linux profiler setup.

The current 3.x Agent does not ship the legacy rgc executable. Do not use old rgc -register, rgc -enable, or rgc -profile automation with the current installer. For Windows Server Core and unattended IIS configuration, use the current Raygun Agent command line.

On this page: