This repo is in the process of being migrated
Please pardon our progress...
We are currently in the process of consolidating our github repos.
See https://github.com/microsoft/ApplicationInsights-dotnet/issues/1214
NuGet packages
Windows:
Linux :
Microsoft Application Insights for ASP.NET Core applications
This repository has a code for Application Insights monitoring of ASP.NET Core applications. Read about contribution policies on Application Insights Home repository
Getting Started
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.
Repository structure
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 targeting NetCore1.1,NetCore2.0 and NET45
WebApi.FunctionalTests - functional tests for Web API application targeting NetCore1.1,NetCore2.0 and NET45
EmptyApp.FunctionalTests - functional tests for an Empty application targeting NetCore1.1,NetCore2.0 and NET45
PerfTest - performance test
Developing
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)
Building
Once you've installed the prerequisites execute buildDebug.cmd or 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.
Testing/Debugging
Execute the 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 intended 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:
"test": "xunit"
Add this initialization logic to Startup.cs:
services.AddFunctionalTestTelemetryChannel();
Branches
- We follow the Git Flow model.
- master has the latest version released on NuGet.org.
- develop has the code for the next release.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.