I've created a plugin system that routes calls from clients into the
particular .Net assembly they request. This will always be late-bound.
I haven't been able to figure out how to debug those plugin DLLs that
are late-bound, though. The .pdb for them is generated, in the same
dir, but any breakpoint I set in the plugin (whether I attach to the
client process or try some other way) always says that the symbols for
this page aren't loaded and the breakpoint will not be hit. Sure
enough, it isn't. Any ideas
Thanks in advance for any help offered.
How can I debug a late-bound C# DLL in VS2005?
Hot Topic
- Excel spreadsheet without toolbar.
- Loading CustomConfiguration section from an addin in Visual Studio 2005
- Another installation error
- Positioning elements generated by a data template on a Grid or Canvas
- Visual Studio 2005, Source Safe 6.0d - web ui not under source control
- Deploying CR IX with Windows Forms Apps
- windows role-based security
- Use IndigoListener.exe in Non-Vista OS?
- How WCF is finding the assembly???
- Item->Property processing
Visual Studio
- Use Microsoft.Office.Tools.Word.Bookmark in a Shared Add-In for Word ?
- VSIP Package Wizard
- About WCF Security
- Client Requirements to run WCF service
- How to set the Tableadapter's method in winform
- IServiceBehavior.ApplyDispatchBehavior
- Logon Failed error
- ANN:VS SDK 2005 Feb CTP for v2
- Embed Word document in VB
- Column and row names
How can I debug a late-bound C# DLL in VS2005?
Scott Ha
A couple things to check:
1. Look in the modules window to see if the module you are delay loading is coming from the right place. (Fullpath is one of the columns). (Debug/Windows/Modules)
2. A right click (context menu) will get you to "Symbol Load information..." This will show you where the debugger looked for symbols for that assembly.
3. If your late bound dll is optimized you may need to turn off "Just My Code". Tools/Options/Debugging/ "Enable just my code (Managed Only).
Steve Steiner
stevejs (at) microsoft.com