.NET Framework Bookmark and Share   
 index > .NET Remoting and Runtime Serialization > Debugging Remotable types in a .NET Remoting application
 

Debugging Remotable types in a .NET Remoting application

Hi everyone,

scenario: I have a simple .NET remoting -> client-server application which shares a remotable type lets say RemoteClasses.dll (containing those types). And reference to this dll is available to both, like in any working remoting application.

Problem: I am unable to hit any breakpoints in themy RemoteClassesproject for debugging, when this project is attached to either of the server or client (calling) applications. "The breakpoints symbolsThe Breakpoint will not currently be hit. No symbols have been loaded for this document".

troubleshooting: Now, I have tried everything Iknew,for example
1. Deleted and reloaded all the referenced .dlls .
2. Delete the .pdb files inobj and bin folders. Recompiled and reRun!!
3. Debug > Windows > Modules. Checked for RemoteClasses module, it says "Symbols Loaded"
4. VS execution mode is set to "Debug"

Can someone point out what could be possiblygoing wrong. If you have done this simple debugging the class lib. project for .NET remoting application, please mention a simple walkthrough. And yes ! I have read the particular msdn thread on debugging the class lib project. IN past I have done debugging of class project via attach process mech, but in this case I have no idea what is going wrong!!! its frustating :(


thanks in advance

-Rupinder
CRM & .NET developer
Rupinder Paul
This doesn't address the error you are receiving but may help in debugging the problem. The method I use to debug windows services may work for you.

1. Add this code to your source code where you want to start debugging:
            // pulls up window to attach to debugger when in debug mode.
            #if DEBUG
                System.Diagnostics.Debugger.Launch();
            #endif

2. Recompile all your assembliesin debug mode.
3. Set your breakpoints.
4. If running from a different locationcopy the debug exe and dlls to that location.
5. Start your app. Whenthe appgets to the code above a window is displayed asking you to select a debugger. Select the running Visual Studio program that has your solution open. This attaches the process to your project.

Hope this helps.
Diane

DPedersen

You can use google to search for other answers

Custom Search

More Threads

• How to properly clean up when done with remoting
• Raising Event - Unable to find Assembly issue
• how to make the client app use a spcific IP?
• server status
• Seserialize binary string to Image
• Memory consumption of objects on server not reducing
• Upgrading from 1.1 to 2.0 and the new ensureSecurity option
• Insert a XmlNodeType.Comment with Serializer
• DataContractSerializer does not deserialize object graph correctly
• Generic serialization of derived/base classes