My application hang and I attached to it from VS .Net 2003 debugger.
I clicked "Break" button in the "Process" dialog. Usually I could break into
my application and see what is happening.
But recently I could not do that for some hung processes. I got the

I am using the Perfomance Tools from Visual Studio 2005 in order to
instrument an EXE and an assembly. Both have been compiled as Release
builds and signed. I added the two files which interest me as target
binaries, added a post-instrumentation "SN" invocation in order to re-

I have a simple visual basic 6 program that calls a function in a class
written in C# assembly. Running executeable directly gives me no
problem, debugging VB6 program is also working fine. However, when I
try to debug C# assembly with VB6 program, VB6 program simply crashes

   I opened  the project from web and build successfully, but i cannot able
to debug the web application. local Machine.
The user is a member of  VS developers,
Administrator.

Will the new DataSet Visualizer work with classes extended from the DataSet
class?

I'm debugging a library which I didn't write, and I'm new to VS.NET
environment, so kinda worst case scenario :)
Somewhere in the code, there is a #if (DEBUG) prepocessor directive like
 this:

Trying to use the VS2005 performance tools as a non-admin seems full
of difficulties. The first one, is that the user has to have the
"Create global objects" right, which can be specified using Local
Security Settings / Local Policies / User Rights Assignment.

What's the actual differnce in output that results from selecting Release
over Debug. I assume that some "debugging" code is left out but am not really
sure what occurs. Is there a way to predict code performance differences
between Release and Debug?

I am a new developer of ASP.NET and I've been using Microsoft Bisual Basic
.NET 2003 for a month or so. I've experienced some problems with DEBUGGING
which are still not solved, and I was hoping someone here could help me.
Everything started when I scanned my computer looking for ...

I have a simple c++ project on platform win32 with visual studio 2005.
When I add simple breakpoints and look at the locals window of the
debugger I see only the parameters of the current function I am in.
However in this function (and before the breakpoint specified) there

greeting,
I Read the article << Improved Error Reporting with DBGHELP 5.1APIs >>
of matt pietrek.
but I found when report crash informations, some local variables and

Extra Info on previous message
Previous message:
I have had instances where changes made while in Edit and Continue mode are
not always saved correctly i.e. a bug is fixed and the code tests ok but on a

When I'm debugging with VS 2005 I often have
the following problem with Debug.Assert.
If an assert fires I cannot look at all the
locals in the callers of the asserting method.

I am running a remote debugging session on a remote machine and am not able
to stop at breakpoints because symbols are missing.
I have installed both .NET Framework and VS.NET Remote Debugging in the
remote machine. What's missing?

I just installed vs 2005 and I am trying to debug regular ASP pages and they
never stop at the break points I put in.
My coleages are able to debug .net programs, but I can NOT do it with ASP
pages.