I'm trying to get remote debugging of ASP.NET v2 web applications
working between my XP Pro (64-bit) machine and Windows Server 2003
(32-bit) and the Visual Studio 2005 Remote Debugger Configuration
Wizard says "The Windows Firewall on this machine is currently blocking

I'm having trouble getting basic debugging enabled for SQL stored procs
from VS.NET 2005.  I've never tried to do this before, so I'm sure this
is just a simple issue.   Here's some background:
I'm on a simple development PC, everything runs local.  I'm using SQL

I recently installed Visual Studio .NET 2005 on a machine that already
had Visual Studio .NET 2003 installed on it. Upon trying to run a
WinForms app in VS.NET 2003 in debug mode (F5), I received the
following error message:

I would like to debug into a .net 1.1 dll that is being called from a 2.0
asp.net app.
I tried the following:
1) Opened VS 2003 dll project

I found that Visual Studio 2005 shows std::map contents like ordinary array
and it is much more convenient comparing to the prior versions which showed
red-black node blahblah. I think VS2005 has a feature which enables
customized watch (I am not saying about Visualizer ...

I have an MFC exe compiled in VS 2005 that is generally compiled without
/clr, except for one cpp. The application uses VBA 6.4 and .NET and COM
objets and at the end (or near) of debugging I am getting repeatedly this
warning:

Debugging in Visual Studio 2003
What I try to achieve is:
I have 2 breakpoints and between those 2 break points a variable whose value
is changed and I want to find which line changes it. I think in vb6, you were

In VS 2003, the command window had intellisense when debuging - i.e.
you could type a command or variable, press ., then get the
intellisense object dropdown for that particular command or variable.
However, in VS 2005 I cannot get this to happen anymore - i.e. if I

When I use the DebuggerDisplay attribute at the assembly level and specify
the Target property, the VS2005 debugger does not display the specified
debug string. For example, I have the following line of code compiled into
my assembly in AssemblyInfo.cs:

I have been told I cannot enable DCOM Remote Access for Anonymous Logon on my
developer workstation, yet that seems to a necessary step in getting remote
debugging operational against web services located on a separate Windows 2003
server.