Start up your application in Debug mode, and check the Diagnostics Tools section after clicking a few links in the application you are debugging (such as the About or Contact links on the top of the page).Īfter checking, if you don’t see any Application Insights events, then you have successfully removed the Application Insights SDK from your web application. Now that you’ve performed one of the two options to remove Application Insights from your application, let’s confirm that Application Insights was removed. Verifying removal of Application Insights locally Once you click on “Uninstall,” a dialog will display that shows all of the unnecessary dependencies to be removed from the application. You’ll also want to remove all dependencies when uninstalling, so click on “Options” and check the option to remove dependencies under “Uninstall Options.” Your screen should look like this: Since Application Insights is a NuGet package already configured for the application, we’re just going to remove it.Ĭlick on the package called “,” and then check the checkbox in the project listing on the right side to select all projects. Option #2: Using the Visual Studio NuGet UIįirst, right click on the Solution and click on “Manage NuGet Packages for Solution.” Clicking this will take you to a screen that allows you to edit all of the NuGet packages that are a part of the project. Uninstall-Package -RemoveDependenciesĪfter entering that command, the Application Insights package (along with all of its dependencies) will be uninstalled from the project. Option #1: Using the Package Management Consoleįirst, open the Package Management Console in Tools -> NuGet Package Manager -> Package Manager Console. Configure using the Visual Studio NuGet UI (a little slower, but more comfortable for users unfamiliar with the CLI).Use the Package Management Console (a little faster but uses the command line).Perform one of two options to remove Application Insights from the application: Now let’s turn off debugging mode and get to removing the package that allows for Application Insights to run. Great! We’ve confirmed that Application Insights is running for your application. You’ll click on the “Events” tab in “Diagnostic Tools” and see something like the following: After creating the web application, start debugging the app, which automatically brings you to the homepage:Ĭlick a few links on the top of the application (such as About and Contact) and then head back to Visual Studio. NET Framework web application using the template provided with Visual Studio.įirst, let’s verify that Application Insights is running for your application. NET Core, Application Insights must be explicitly installed.įor this guide, I’ve created a. NET Framework, Application Insights is likely installed by default alternatively, with. A quick side note on this-if you’re using a. To follow through the rest of this guide, you’ll need We’ll confirm the removal of Application Insights both on the. So you’ve decided to remove Application Insights from your application. NET Framework, Visual Studio adds a bunch of junk to your project.īelow are a couple screenshots showing the nfig and added project dependencies. But on a brand new project for ASP.NET on the full. Okay, perhaps calling it a virus is a little harsh. Let me remind you again-if you’re going to skip performance monitoring with Application Insights for a production application, make sure you have something else in place! Application Insights is like a virus… For example, you may choose to look into Retrace, which is more fully featured and provides more functionality out of the box. It may be unnecessary to use Application Insights for applications being hosted in development or staging environments since those environments will not have significant performance concerns.įinally, you could just not want to use Application Insights for performance monitoring and may have other means of monitoring your application.When working with your application locally, you may find that the information provided is verbose.Using Application Insights with Azure comes at a slight cost, depending on the traffic that the web application provides.With that in mind, here are a few reasons why you might want to remove Application Insights from your application: In my experience, this is generally the case-the benefits typically outweigh any issues that may come from having them in place. Microsoft claims that the overhead of adding Application Insights to a project is quite low. When considering to remove a tool that helps with monitoring, it’s worth thinking why you might want to do this.