Debug custom dll that is being referenced in visual studio macro

Question

I previously asked: Add dll reference to visual studio macros

the idea of creating the macros in my language (C#) makes it easier to create the macros. The prob

Answer 1

Tono,

Have you referenced your dll for the wcf application and made it a debug version?

From: http://msdn.microsoft.com/en-us/library/ms164704.aspx:

No matter how you start debugging, make sure that you build the Debug version of the DLL first and make sure that the Debug version is in the location where the application expects to find it. This may seem obvious, but if you forget this step, the application might find a different version of the DLL and load it. The program will then continue to run, while you wonder why your breakpoint was never hit. When you are debugging, you can verify which DLLs your program has loaded by opening the debugger's Modules window. The Modules window lists each DLL or EXE loaded in the process you are debugging. For more information, see How to: Use the Modules Window.

---

If you are attempting to debug a referenced dll, this SO article might be of assistance here: How to debug a referenced dll (having pdb)

~JOL