I have an ASP.NET web application, and some operations are 6 times slower in full-featured IIS 8.5 on the server and in Visual Studio IIS Express.
If I try to connect for just debugging, I see correctly w3wp.exe:
I do not see w3wp.exethe "Attach the profiler" dialog box.
I am running VS 2017 with administrator privileges. This is not a remote debugging scenario, and full IIS, and debugging tools are on the same server (if it is important for Windows Server 2012 R2 Essentials). I am using Visual Studio 2017 Community Edition.
IIS, , 6 ? , : , .
BTW . , , 16 ( , ) . , IIS , SQL Server .. , , . VS IIS Express BTW. , Visual Studio 2015 .
Rob was pretty brief. First, you need to run Visual Studio in administrator mode. In addition to choosing ASP.NET as the goal of analysis at the beginning, as soon as the profiling wizard appears on page 2, you need to select the “ASP.NET application” again instead of your available project, otherwise Visual Studio will simply start the server. After that, on page 3 of 4, I will indicate the URL of the website of the application launched by my local (non-developer) IIS server ( http: // localhost: 8000 ). Here you must restart VS in administrator mode if you have not already done. Then Output Performance looks as if VS started another server:Preparing web server for profiling.
Profiling started.
Launching web server with profiling.
Profiling process ID 872 (w3wp).
Starting data collection. The output file is C:\Users\Csaba\Documents\MyProjectSrc\http_localhost_8000__170924.vspx
Profiling process ID 8416 (iexplore).
Attaching to process 8416.
Profiler stopping.
Stopping data collection.
Merging collection data. Please wait...
Data is saved in file C:\Users\Csaba\Documents\MyProjectSrc\http_localhost_8000__170924.vspx
Profiling finished.
, , . , . 100% , .