Is it possible to debug IIS without affecting all users of the service?

This may seem like a silly question, but we have a problem debugging IIS in a common test environment, and I hope someone there can give us an answer.

We have Windows Server 2003 running IIS 6 and sharepoint 2007. We are debugging locally on the server with Visual Studio 2008.

When someone attaches a debugger and goes through the code, we find that all users are affected. In fact, the web server stops processing all requests from all users.

Our question is, is this a typical situation and should it be expected? Or there is some kind of configuration that we can change that would allow us to debug one user session, but the rest remained unchanged.

+3
source share
6 answers

Kev is on the right track. You need to make sure that the project that you want to debug separately from others is in its own application pool. This isolates it to its own process and allows you to stop or debug the process without affecting other applications that may remain in another pool.

Customization

  • Start → Run → inetmgr
  • Right click on application pools
  • Click Create → Application Pool
  • What is the new pool
  • Right-click the application that you want to isolate.
  • Click Properties
  • Go to the Home Directory tab
  • ""

- , , .

, w3wp.exe , :

  • → → cmd
  • iisapp
  • CScript, , "" .

, , , aspnet_state, , .

+4

" - , . - .

, , inetinfo.exe w3wp.exe, , / , , , .

+1

. , ?

0

. debug.mydomain.com, . , , , - - .

/ , . , , , asp.net . , , , .

0

, visual studio , . , , YMMV .

0

AFAIK. web- node - /. , .

0

Source: https://habr.com/ru/post/1723407/


All Articles