S
Siegfried Heintze
I used to be able to just hit F5 to debug my ASP.NET
applications on my notebook.
But since I installed MSOffice 2003, I get that silly
error message about a catastrophic failure when
starting the debugger.
I discovered I could start the project without the
debugger and connect to it later using the processes
menu entry in visual studio. But that is tedious.
The help message gives a long list of things to check.
Most of them don't apply (I'm running under the
Administrator account, there is a web.config that I
have not touched, I have not changed which account
anything runs under, I specified the server name as
localhost, remote services must be installed because
it was working before and IIS was installed before
Visual Studio.NET was insalled).
I was thinking about installing VS.NET 2003 again. Do
you think that would fix the problem? It is such a
long process, however!
Has anyone else encountered problems after installing
Office 2003?
thanks,
Siegfried
applications on my notebook.
But since I installed MSOffice 2003, I get that silly
error message about a catastrophic failure when
starting the debugger.
I discovered I could start the project without the
debugger and connect to it later using the processes
menu entry in visual studio. But that is tedious.
The help message gives a long list of things to check.
Most of them don't apply (I'm running under the
Administrator account, there is a web.config that I
have not touched, I have not changed which account
anything runs under, I specified the server name as
localhost, remote services must be installed because
it was working before and IIS was installed before
Visual Studio.NET was insalled).
I was thinking about installing VS.NET 2003 again. Do
you think that would fix the problem? It is such a
long process, however!
Has anyone else encountered problems after installing
Office 2003?
thanks,
Siegfried