Microsoft Application Insights for ASP.NET Core applications
Application Insights monitoring is a service that allows you to collect monitoring and diagnostics information about your application. The getting started guide shows how you can onboard your ASP.NET Core web application to use the Application Insights SDK.
Application Insights collects a lot of information out-of-the-box such as requests, dependencies, exceptions, and usage. It also allows you to configure additional data collection. The configure guide demonstrates the most common tasks you may want to do.
root\ ApplicationInsights.AspNetCore.sln - Main Solution src\ ApplicationInsights.AspNetCore - Application Insights package test\ ApplicationInsights.AspNetCore.Tests - Unit tests FunctionalTestUtils - Test utilities for functional tests MVCFramework.FunctionalTests - functional tests for MVC application targetting NetCore1.1,NetCore2.0 and NET45 WebApi.FunctionalTests - functional tests for Web API application targetting NetCore1.1,NetCore2.0 and NET45 EmptyApp.FunctionalTests - functional tests for an Empty application targetting NetCore1.1,NetCore2.0 and NET45 PerfTest - performance test
To successfully build the sources on your machine, make sure you've installed the following prerequisites:
- Visual Studio 2017 Community or Enterprise. Please make sure to install all the latest updates to Visual Studio
- .NET Framework 4.6
- .NET Core SDK 1.1.7
- .NET Core SDK 2.0 or above.(https://www.microsoft.com/net/download/windows)
Once you've installed the prerequisites execute
buildRelease.cmd script in the repository root to build the project locally.
You can also open the solution in Visual Studio and build the ApplicationInsights.AspNetCore.sln solution directly.
RunTests.cmd script in the repository root.
You can also open the solution in Visual Studio and run tests directly from Visual Studio Test Explorer. However, as the tests has multiple targets, Test Explorer only shows the first target from in .csproj. To debug/run tests from a particular TargetFramework with Visual Studio, only option is to re-arrange the such that the intented target comes first. This is a Visual Studio limitation and is likely removed in the future.
Running and writing tests
There are two sets of tests unit tests and functional tests. Please use unit tests for all features testing. The purpose of functional tests is just end-to-end validation of functionality on sample applications.
Functional tests Functional tests are regular web applications with unit tests integrated into them. Application can be compiled as a regular web application as well as set of tests. Typical functional tests will do the following:
- Host the current project in In-Proc server.
- Initialize application insights telemetry channel.
- Initiate request to self hosted web application using HttpClient.
- Check data received in telemetry channel.
The following are modifications made to a regular web application to make it work this way:
Add dependencies to .csproj:
"FunctionalTestUtils": "1.0.0-*", "dotnet.test.xunit": "1.0.0-*", "xunit": "2.1.0"
and test command:
Add this initialization logic to Startup.cs:
- We follow the Git Flow model.
- master has the latest version released on NuGet.org.
- develop has the code for the next release.