In older versions of Visual Studio there was a way to avoid certain
functions while debugging. This was especially useful for functions that
were part of atl or mfc such as "PXSTR GetBuffer()".
Is it still possible to do this in VS.Net 2003, and if so, how is it done?

Does somebody maybe knows of it is possible to add my own tracelistener
to the traceSource using the config file? I'm using vs2005 b2, and
wrote a tracelistener that i want to use as a 'normal' tracelistener in
the config file (Adding the listener to the tracesource with

I'm trying to get SQL debugging up and running. We have remote debugging
working fine but when we try and use SQL debugging the following message
displays:
Unable to start SQL debug session. Ensure sqldbreg2.exe and proxy/stud DLL

I have a Windows 2003 standard server that is used mostly for testing and
debugging. I installed SP1 when it was first released and it killed
debugging. I wasted about a day looking for the solution and then
uninstalled SP1. Everything worked again.

I saw a demonstration of the beta version of VS 2005 and it had a neat little
tool called "Performance Tools" that would show you a lot of info about a
program, including what functions were taking the most time.  Does anyone
know if there is a way to get this on VS 2003?  

When I try to debug an asp .Net web site from my machine (the website is on
an IIS 5 server),  get the folowing error
------------------------------------
Unable to connect to the machine 'mymachine'. The RPC server is unavailable

I have a computer that I'm an administrator of.  I can run in debug
mode.  I have  other people who I need to develop that have remote
desktop priviledges to this machine.  However, I don't want them as
administrators.