I'm having an issue where VS 2005's debugger hangs when entering an event
handler method for a DateTimePicker control.  I have a pretty basic main form
that has a DateTimePicker in a tab control and I added an event handler for
the ValueChanged event.  Initially I noticed this ...

I am trying to develop ASP .NET 1.1 apps using VS 2003. When I press F5, I
get the following output:
'DefaultDomain': Loaded
'c:\windows\microsoft.net\framework\v1.1.4322\mscorlib.dll', No symbols

From what I have  read the Command window is similar to the Immediate Window
in MS Access, thus you can type in the name of a function prefixed with a ?
and run the function while the application is NOT running. For example, to
test this, I created a PUBLIC Function Adding(byval ...

I have a plain executable that I'd like to debug remotely.
The machines are on diferent domains so I have chosen to use native transport with no authentications (although I configured the required users, but there was a firewall problem for DCOM communication)
On the remote machine ...

I've been trying to put to use some Global Compilation Constants. From what I
understand, I set them up in the Advanced Compiler Settings dialog in the
Custom Constants Filed. The name of my Solution Configuration is DebugOpt and
the proper one is selected. My Constant is ...

On one form in my project, when attempting to debug, after the process starts
it automatically removes my breakpoint from the form. If I attempt to put it
back after it has started, it opens a new instance of the code view and
places the breakpoint at random locations on that ...

(this is a repost under managed newsgroup alias)
How do I configure ADPlus to give a full dump on a CTRL+C command window?  I
know minidumps are the default behavior.
Thanks in advance for the help.

When my code has all the necessary include files, I receive the above
error.  In trying to isolate the error, I remove all include files
except windows.h and still receive this error in Visual Studio 2005.

Windows XP Professional x64 Edition has crashed many times the last year and
two months.
I have made available 27 minidumps that were made during the crashes !
Not all minidumps might be complete, sometimes I resetted the system because

I have a major problem when working with VS.NET 2005 debugger on large
projects. Very often, the debugger is not able to evaluate any watch
expressions for no apparent reasons.
The code is compiled in debug mode, and all I want to do is to

I've somehow lost my keyboard shortcuts for VS debugging (F5,F10,F11,etc.).
Does anyone know how to reset these?
I've tried :
Tools | Options | Keyboard | Reset

In Visual Studio under Debug | Attach To Process In the Attach To Process
Dialog there are a list of processes, one of the columns is "Title", what is
the Title?  Is it the Caption of the MainWindow for the Process?  Is it the
process name?