We're using Visual Studio .NET 2003. The project is c++, plain Win32,
no MFC. We are using Redhats pthread implementation for Win32 as we
ported over an app from Linux.
When we debug we'd like to view such things as pthread_mutexs etc..

I can quite happily debug web projects with Visual Studio 2003, but for some
reason the debugger just detaches from from the process for no apparant
reason.
I can't re-attached either as it tells me something along the lines of there

I want do debug my project ( one .exe and some .dll´s ).
The debugger show me source files from the wrong path.
I have build the project in my source path.
All Files ( .exe .dll .pdb .c ) are then copied to my test path, all in one

I have a solution in vs2005 converted manually from vs2003. I did not use
the conversion wizard. When I try to set a break point on a web page I get
the message when mousing over the break point "The breakpoint will not
currently be hit. No symbols have been loaded for this ...

Is it possible to use Visual C++ 6.0 or Visual Studio.NET 2002/03/5 to do
parallel compiles/building across many PCs? I find my building/compiling
takes years.
Last year when I was developing on linux I came across distcc, distributive

I have a page called HelloWorld.aspx and it accesses a public method in a
helper class called MyClass.cs.  When I open the
http://localhost/HelloWorld/Trace.axd page, the Trace.Write statements in
the HelloWorld.aspx page show up, but the Trace.Write statements I put in

I'm facing a strange problem.
I debug an asp.net web site. The web site is located on a server (win 2003) and
I debug from a XP Pro station. Both belong to the same domain (the server is
also the DC) and I'm logged on the XP station as a domain administrator.

I recently uninstalled VS 2003 and installed C# 2005 express edition.  I
really like C# Express, but I'm having a problem with the debugger.  When it
throws an exception, it tells me "An exception (exception name) has occured
in (project.exe) However, no debuggers are registered ...

Currently, our team is looking at remote debugging for managed code using
VS2003 .Net (Enterprise Architect). Our scenario is that we need to debug
some remote processes (developed in C#) from our workstation, and for some
cases, the remote machines are in different domain.

Hello NG,
I've trouble to to debug a vb.net application implementing a com interface.
<ComClass(ComClass2.ClassId, ComClass2.InterfaceId, ComClass2.EventsId)> _
Public Class ComClass2

I'm running a multi-threading service in C#. When the service stops, the
following often (but not always) happens:
1. The OnStop method runs through without any errors.
2. The Service.Dispoes method runs without any errors.

All of a sudden I noticed that my Trace stattements did not write anything in
the Output Window.
I checked with the code found at http://support.microsoft.com/?id=815788 and
the Trace and Debug statements did only work in the consol applications

We have a solution with a web project and several class libraries (business
logic, db access, custom controls, etc). The web project references the class
libraries and uses them to do most of the processing.
We can use the "Edit and Continue" function with no problem in the web

Posted this to the SBS group, but was directed back to Visual Studio
group by MS support.
Installed SP1 on my SBS 2003 server Saturday.  Took me all week to get
my arms back around things, and now that I have (maybe) I set about to

When trying to debug a console app remotely I get this error:
"Unable to attach to the process. Attaching to process in other users
sessions is not allowed.  Administrators can enable this feature.  Consult
the help for more information."