Visual Studio 2010 and IIS Express lock during assembly

I have about four web projects that I host on IIS Express. Whenever I make an assembly in Visual Studio 2010, the assembly will be blocked until I manually destroy IIS Express. Then the assembly is complete. A new instance of IIS Express is created, which works as expected.

I tried to execute the prebuild event to kill IIS Express using taskkill, but the lock seems to happen before the pre-build event is executed: /

If I stop hosted sites, Visual Studio 2010 will also work as usual.

From researching one of the possibilities is that IIS Express tries to display a dialog in which Visual Studio 2010 expects user interaction, but does not actually display a dialog box.

Has anyone else had a problem blocking IIS Express and Visual Studio 2010 during creation? Or some understanding of how to debug this problem?

+4
source share
3 answers

If I remember correctly, the latest service pack for vs 2010 fixed this error (at least on my machine).

+2
source

Visual studio seems to be trying to do something on port 80, which IIS blocks (this is the default listening port for it).

A simple google search on port 80 of the visual studio causes some promising hits (how to configure it, and hey! 2nd even has a fix for a similar problem.)

0
source

This happens to me constantly, but again I use WinXP / VS2010 / IIS Express 7.5. I suspect that part of WinXP is the culprit, perhaps a mistake for this particular scenario? Anyway, VS2010 wants to rebuild one of my web applications, but it seems to be waiting indefinitely on some ASP.net temporary directory files for the web application until I stop IIS Express.

0
source

All Articles