Artem Vertiy
Reputation: 1118
Visual Studio 2015 debugging attach to local IIS - Managed IIS APPPOOL process not found
I have just migrated from 2013 to 2015. I used to attach debugger to local IIS site by selecting process by User name, but VS 2015 does not show in the list IIS APPPOOL[AppPoolName] managed processes.
Upvotes: 1
Views: 1849
Answers (1)
Artem Vertiy
Reputation: 1118
Find w3wp.exe process, click attach on it. VS will ask you to run with Administrator permissions. After VS is run from Administrator you will be able to see IIS APPPOOL \ [AppPoolName] managed processes in the list.
How to make it always run as Administrator look here
Upvotes: 2
Related Questions
- Visual Studio 2012: Unable to attach the process. A debugger is already attached
- Visual Studio Debugging is stuck at "Attaching to the web server"
- Asp.Net Core: Debug -Attach to process is not working
- VS2015 Unable to connect remote debugger
- visual studio error attaching debugger
- Why an IIS 10 Application pool is created when I start debug through Visual Studio 2017 (15.7.3)?
- Debugging Azure: Error attaching the debugger to the IIS worker process
- Attach To Process w3sp.exe and choosing AppPool
- Visual studio does not recognize aspnet_wp.exe when attaching to process
- Debugging w/ Attach to Process Starts ASP.NET Dev Server