I installed VS.NET 2003 on my XP Home computer expecting it
to be a replacement for Visual C++ 6 Pro that I had (and
still have) installed. Just to play around with it and see
what's new, I created a simple test Win32 Console

I have a large project that contains a large number of folders and files
that have the same name.  (ie default.aspx is in \Folder1, Folder2, etc)  I
usually have no problem debugging the code, but on occasion, if I try to set
a breakpoint in the code in \Folder1\default.aspx.vb, VS ...

I get this message when trying to debug the hello world
app in the walkthru (or any other SDE application).
Launching Application
Error while trying to run project: Unable to start

The MSDN technical article, Post-Mortem Debugging Your
Application with Minidumps and Visual Studio .NET, by Andy
Pennell, March 2002, mentions associated project files but
there is no active link.  Anyone know where these files

I have a C++ project which is composed of a single .exe
and multiple .dlls.  I changed my Visual C++ project to
Use Managed Extensions and added a couple of lines of
Managed C++ to one class to call a .NET web service.

   Dr. Watson helps us to save 'crash dump' on the hard
disk, so the .NET programmer will be debug exactly the
situation of the user.
You can config the Dr. Watson to save the 'crash dump' in

ASP.NET VISUAL BASIC on Windows 2000 Professional
Problem:
1. change a variable say,
DIM strCmd as string

Iam using Visual Studio C++ .NET 7.1
While debugging a program, I noticed that stack trace is empty when
the program crashes.
I get a dialog

...WHY...
(bet you knew it was going to start with that...)
...WHY does setting the System.Diagnostics.DebuggerStepThrough attribute for
a method result in debugging that steps OVER that method?

VS .NET 2003 Pro
VC++
Hi,
I have a program that when it is ran it loads a dll using LoadLibrary, then it runs a selected external program by creating the process. Once the process has been created the dll then hooks itself into the created process. The problem is the breakpoints I ...

I can't use debugger to check ASP.NET code. When I start debug,
sometimes devstudio hangs, sometimes I get error: "Auto-attach to
process '[3852] aspnet_wp.exe' on machine 'MYMACHINE' failed. Error code
0x80010012". Sometimes it helps when I kill aspnet_wp.exe process, but

Iam not able to debug applications using the vs.net -
(even the new applications with just  a "response.write").
Iam have a windows 2000 professional machine and the user
is an administrator and part of the debugger users.

hopefully this posted mail will be read by a microsoft
developer.
I'm writing a monitor application (native Win32), which
uses the ICorDebug

I'm a newbie to this newsgroup, so excuse me If I repeat
well-known things. Why the performance of unmanaged
debugging under VS.NET is so sluggish? I'm developing an
add-in for VS.NET, so I have to enable unmanaged

I am new to using C# and MSVS for my development.  I have
written a simple program that uses various Windows form
components that works as intended on the Windows XP
machine that it was developed on.  I built a Release