Hi Norman,
> One Visual Studio 2005 solution contains a C# project and C++ ATL DLL
> project. The DLL compiles fine, gets registered automatically, gets
[quoted text clipped - 6 lines]
> valid. I can right-click the dot and set an option for the "place" of the
> breakpoint, but it doesn't matter. The breakpoint never gets hit.
Two things:
1) are you using debug builds?
2) did you enable mixed debugging for managed und unmanaged code?
Project->Properties->Debug "Enable unmanaged code debugging"
--
SvenC
Norman Diamond - 19 Sep 2007 09:06 GMT
> Hi Norman,
>
[quoted text clipped - 11 lines]
> Two things:
> 1) are you using debug builds?
Yes of course.
> 2) did you enable mixed debugging for managed und unmanaged code?
> Project->Properties->Debug "Enable unmanaged code debugging"
That was almost enough information to find it. Thank you. I know not to
shoot the messenger for this incredibly bad design, and I thank you for
informing me.
The solution has two projects in it. Visual Studio's options, Tools -
Options - Debug, don't do anything to prevent debugging (I suppose they
could be set to prevent debugging but I didn't do so). In the DLL's
properties, the debug options don't do anything to prevent debugging. You
described an option which is available in the C# project's properties. In
order to debug project #1, it's necessary to right-click project #2 and set
project #2's properties to enable debugging of project #1. What an easily
discoverable (not) way to stop breakpoints from breaking in project #1.
Coming next: To shut down your computer, don't click Start on your
computer, but click Start on your neighbour's computer.