>
>If you still don't hit the breakpoint, and you've already followed the instructions in the MM .NET Dev Guide topic "Stepping through MM .NET code in the Debugger", try adding the MM .NET project to your solution. You can specify that the MM .NET project is not built by doing the following (this is due to an "isssue" in VS .NET):
>

Any suggestions when that also fails? I >really< hate this bug in VS.Net. It's a major PITA and I seem to always run into it. In the case of some other classes, I've actually had to compile them into my app. (eg. leave the "Build" option checked) before being able to debug them. In the case of MM's, since we don't have the signature key, I can't easily do that without gen'ing my own key (which I don't want to do).