1. Installation Guide

• Create a new Application Insights Instance (https://portal.azure.com) and write down Instrumentation Key as well as the AppId and ApiKey.
• Load the PerfViz's code-base into VS. To compile, Visual Studio requires Extension Development Tools that can be installed via the Visual Studio installer (that is also used to update Visual Studio). Inside AzureTelemetryProbe's code body, enter the instrumentation key in the field provided. Build the complete solution (Release).
• Install the InSituVisualization Plugin into VisualStudio (that you just built inside the repo), restart, and enter the AppId and ApiKey (under Options --> In Situ Performance Visualization).
• Inside the software that should be monitored: Add a new reference and point it to the AzureTelemetryProbe's .dll file location (<Path to the Repo>\visual-studio-perfviz\AzureTelemetryProbe\bin\Debug\AzureTelemetryProbe.dll).
• Inside your software's build properties, under build events, add a new post build event: cd <Path to the Repo>\visual-studio-perfviz\ProbeInjector\bin\Release\ ProbeInjector.exe -p <Path to the Repo>\visual-studio-perfviz\AzureTelemetryProbe\bin\Release\AzureTelemetryProbe.dll -r <Path to your Software Repo>\<Name of the Repo>\src\Web\obj\Release\<Path to .dll, .exe> This post build event injects the needed logging statements into the executable or library that you want to monitor.
• Your Software will now be injected if either being published or run as Release. If Debugging is required, the path behind -r can be adjusted to point to the folder "Debug".

Beware: It will take a few minutes until the data is available and shown in Visual Studio.