Wierd situation here.  Running ASP.NET 1.1 on Win2003 SP1.  I have to
manually
attach the debugger to a process in order to debug.  So I set a breakpoint
in an obvious place (like within the Page.Load event) that will catch it.

 I try to install C# window service in orther PC by using installutil my
service.exe,
I got following error:(This PC already have other C# window service
installed)

I am new to ASP.NET (VB) but have previously programmed a lot in VB. I am
running across a strange problem but cannot seem to figure out what is
causing it. I am curious to know if anyone else has come across the same
problem.

I have a class that holds a static char* array and an index :
class Name
{
   static char* array[100];

MailMessage mailMsg = new MailMessage();
mailMsg .From = "From";
mailMsg .To = First.Last@Mycompany.com
mailMsg .Subject = "Subject";

   I was able to debug with no problems until I tried to debug this one
time and the IDE froze. I killed the aspnet_wp.exe service and then restarted
IIS and the IDE came back, but I couldn't do anything so ended the task.
When I restarted VS 2003 and tried to debug I got the ...

I'm running Windows 2003 Server SP1. I have installed SQL Server 2000
SP4 last Sunday. Since this patch has been installed cannot run any
.NET project (windows services, console, ...) in debug mode.
I have checked this article on MSDN :

Have a small SBS2K3 sp1 rc1 domain, wanting to remote debug with multiple
domain users (3) from multiple workstations (XP Pro sp2) using VS2K3. At
this point can remote debug, but the user doing the debugging has to be
logged on to the server at the time. If user isn't logged ...

I'm writing a VB.Net data app with ADO.Net, in addition to pulling most of
my remaining hair out, I can't find the old F8 from VB single step command
in Debug.  What happened????  F5 to continue is there......  Don't tell me
that the F8 function is gone.

We have an ongoing problem debugging our ServicedComponent. This is a
follow up to the thread entitled: "Unable to debug interop". I want to
restate the issue because in that previous thread, we solved one
problem, we now have another separate problem.

unable to debug/interop
Scenario
1. We have a VB6 application that performs late-binding on a .NET
interoperable component. Our component is invoked as in-proc process.

Using VS.NET 2003.
I have an ASP.NET page in C# which calls a managed C++ remoting object.  I
am trying to step into the managed C++ remoting object with the debugger,
but the debugger can't figure out where it is once I step into the function.

I'm getting "compiler failed with error code 2000" intermittently when
attempting to debug a solution.  The error message details indicate that the
compiler is trying to find a dll (which one in particular varies) in a
Temporary ASP.NET folder that does not exist.   Generally ...

I am trying to debug a VB6 com plus component from Asp.NET but I can't
step through the VB6 code. Any ideas on why this could be?
I currently have both asp and asp.net pages in the same web app. I I
can debug both types of pages. I can also debug my com plus dll from a

I'm looking for any informations about how VS toggles in
debugger mode and it's relationships with mdm.exe
Is there any paper about this topic?