Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio 2017 Network Diagnostics Tool not applicable

I have a WPF project in Visual Studio Community 2017 and I would like to enable the Network diagnostics debugging tool but it is under the list "Not Applicable Tools" in the Performance profiler... menu, with the following provided reason: Network tool does not support the selected target. The selected target is Startup Project

Is there a way to make my project "applicable" without changing the selected target?

EDIT: I gave up on using the Network Diagnostics tool and ended up using Telerik Fiddler.

like image 233
HarshWombat Avatar asked Apr 02 '18 18:04

HarshWombat


People also ask

How do I enable diagnostic tools in Visual Studio?

When you start debugging in Visual Studio by selecting Debug > Start Debugging, or pressing F5, the Diagnostic Tools window appears by default. To open it manually, select Debug > Windows > Show Diagnostic Tools. The Diagnostic Tools window shows information about events, process memory, and CPU usage.

How do I run a performance profiler in Visual Studio?

Open the Performance Profiler by choosing Debug > Performance Profiler (or Alt + F2). For more information on using the CPU Usage or Memory usage tool in the Performance Profiler vs. the debugger-integrated tools, see Run profiling tools with or without the debugger.

What is diagnostic tool in Visual Studio?

The Diagnostics Tools feature of Visual Studio provides you with historical information about your application in a debugging session.


1 Answers

At some point in the past, only UWP apps were supported by the Network profiling tool:

The Visual Studio Network diagnostics tool collects data about network operations performed using the Windows.Web.Http API [...]

The Network tool supports only UWP apps. Other platforms are not supported at this time.

-- 11/03/2016

It seems unlikely that other platforms will be supported, since the network tool relies on the fact that these projects make use of the "WinRT HttpClient APIs."

I can tell you that the tool was introduced in VS 2015, and that I'm seeing the same result as you with my project (a console app) in VS2015 Professional.

like image 176
jpaugh Avatar answered Sep 20 '22 17:09

jpaugh