Hey all,
I have no idea how this started, but at one point in time, starting a
process in Visual Studio 2008 has become a problem.
At first, I was unable to debug a WebService project of mine. I simply got a
"can't start debugging" error.
Then, I couldn't start debugging a Windows Forms application, getting a
"Error while trying to run project: Unable to start debugging."
Now I can't debug any ASP.NET project (including Web Services projects),
getting an error stating: "Only one usage of each socket address
(protocol/network address/port) is normally permitted."
Console application projects seem fine whenever they feel generous enough to
let me debug them.
The *.vshost.exe process is up and running uninterrupted and, of course, I
can't attach to that process to debug after starting it.
Trying to debug the Windows Forms application with unmanaged code last week
has just thrown an error stating that the debugger couldn't debug the
application.
Fixing the Visual Studio installation hasn't helped.
I've gone as far as uninstalling and reinstalling the whole of Visual
Studio. This morning I found the only thing that has changed is that using
the unmanaged debugging trick works. The rest still doesn't.
I'm running a fully patched Vista x86 machine (sans SP1). The only thing I
can think of that is 'dangerous' that I installed would be Linq to XSD alpha
0.2.
All help would be greatly appreciated.
Omer van Kloeten
NuConomy
NuConomy - 24 Mar 2008 09:07 GMT
Just to add, some ASP.NET projects now raise the following error when trying
to debug them:
"Unable to start program 'C:\Program Files\Common Files\Microsoft
Shared\DevServer\9.0\WebDev.WebServer.exe'."
Omer
NuConomy
> Hey all,
>
[quoted text clipped - 29 lines]
> Omer van Kloeten
> NuConomy