Debugging a remote machine

[Guy Noir]

Hello.

I am trying to debug remotely for the first time.
I have 2 machines, identical credentials.

Machine 1: Running VS2005.Net
Machine 2: Running msvsmon.exe from a network share pointing to Machine
1.

On machine 1, I can point to machine 2 and attach to the process just
fine. However, I get the message that says:

The following module was built either with optimizations enabled or
without debug information:
C:\Program Files\Default Company Name\GDLoggerInstaller\GDLogger.exe
To debug this module, change its project build configuration to Debug
mode. To suppress this message, disable the 'Warn if no user code on
launch' debugger option.

This project is indeed built as a debug build.

What am I doing wrong?

Thanks in advance!
-A

[Alan Pretre]

"Guy Noir" <ah******@gmail.com> wrote in message
news:11*********************@g44g2000cwa.googlegro ups.com...

On machine 1, I can point to machine 2 and attach to the process just
fine. However, I get the message that says:

The following module was built either with optimizations enabled or
without debug information:
C:\Program Files\Default Company Name\GDLoggerInstaller\GDLogger.exe
To debug this module, change its project build configuration to Debug
mode. To suppress this message, disable the 'Warn if no user code on
launch' debugger option.

This project is indeed built as a debug build.

Hi. Not sure about your specific problem but two things to watch out for...
You have to be very positive that the version on the remote machine is
EXACTLY the same build that you have on the local machine (that you have in
the debugger), then also make sure that the .pdb files are also on the
remote machine with the binaries.

-- Alan

[Guy Noir]

Brilliant. Copying the .pdb files over has solved the remote debugging
issue.
Thanks for the help!
-A