Debugging an AD DLL out of process
I am able to launch the executable from within the MSVC++ debug environment, but run into the following:
1. I cannot set up any breakpoints. They are removed right before the program starts.
2. As the debug is starting, I get several (probably 40) similar error messages saying "no symbolic information found"
for a specific executable or DLL (mmc.exe and ntdll.dll being the first two). Now I'm thinking that this has to do with
the fact that no breakpoints are being considered. Possibly, I don't have the debug versions of the DLL, but I'm not sure
if this is the case because I downloaded the Microsoft SDK very recently.
Another question I have is this: the DLL must be build in 'Minimum Dependency Mode' when registering onto the server
running AD, since when I switch the configuration to Debug and build it, the DLL registration fails. Now, even though I
registered the DLL that was built in Minimum Dependency Mode, I switch to debug mode and run the debugger from
that mode, (since I don't think you can debug in Min. Dep. Mode). My question is here: are the breakpoints being ignored
in the debug version since a completely different dll is being run (namely the registered Min. Dep. one)?
Any help would be greatly appreciated.
Naz

