remote debugging
-
hi, does anybody know that .net version can cause a problem in remote debugging ? i have .net 3.5 in my client and in other machine i have .net 2.0 without development tools like visual studio or other i want to debug a large scale windows application developed in C# and .net 2.0 . i used msvsmon in target machine and i want to attach the process (win service in my project). i can see it in my 'attach to process' window's process list and i attach it . but it does not work. does .net framework versions cause this problem ? tanks.
--------------------- Areff Bahrami(KAVEH) Areff.HB@Gmail.com ---------------------
-
hi, does anybody know that .net version can cause a problem in remote debugging ? i have .net 3.5 in my client and in other machine i have .net 2.0 without development tools like visual studio or other i want to debug a large scale windows application developed in C# and .net 2.0 . i used msvsmon in target machine and i want to attach the process (win service in my project). i can see it in my 'attach to process' window's process list and i attach it . but it does not work. does .net framework versions cause this problem ? tanks.
--------------------- Areff Bahrami(KAVEH) Areff.HB@Gmail.com ---------------------
Areff wrote:
but it does not work.
Be more specific. Do you get any error messages? if so what?
Yusuf Can I help you?
-
hi, does anybody know that .net version can cause a problem in remote debugging ? i have .net 3.5 in my client and in other machine i have .net 2.0 without development tools like visual studio or other i want to debug a large scale windows application developed in C# and .net 2.0 . i used msvsmon in target machine and i want to attach the process (win service in my project). i can see it in my 'attach to process' window's process list and i attach it . but it does not work. does .net framework versions cause this problem ? tanks.
--------------------- Areff Bahrami(KAVEH) Areff.HB@Gmail.com ---------------------
Make sure you have the .pdb files available for the assembly you're trying to debug. If for some reason it doesn't automatically load the symbols, open the Modules window, right-click your assembly name and select "Load Symbols" and select the pdb file. Make sure the source code you have open, the pdb file, and the assembly versions all match up, otherwise you won't be able to load the symbols or hit any breakpoints. Dybs
-
Make sure you have the .pdb files available for the assembly you're trying to debug. If for some reason it doesn't automatically load the symbols, open the Modules window, right-click your assembly name and select "Load Symbols" and select the pdb file. Make sure the source code you have open, the pdb file, and the assembly versions all match up, otherwise you won't be able to load the symbols or hit any breakpoints. Dybs
tnx Dybs after attaching i see this message on every breakpoint. The breakpoint will not currently be hit. no symbols have been loaded for this document does this is for .pdb files ?
--------------------- Areff Areff.HB@Gmail.com ---------------------
-
Make sure you have the .pdb files available for the assembly you're trying to debug. If for some reason it doesn't automatically load the symbols, open the Modules window, right-click your assembly name and select "Load Symbols" and select the pdb file. Make sure the source code you have open, the pdb file, and the assembly versions all match up, otherwise you won't be able to load the symbols or hit any breakpoints. Dybs
hi, and tanx Dybs i done this job with copying the pdb files to the target machine and it's ok now.
--------------------- Areff Bahrami(KAVEH) Areff.HB@Gmail.com ---------------------