how do I do this? I am certain my Visual Studio .NET solution allowed me to
do this before but I don't know how the build/debug settings were
configured.

In order to get around an unavoidable circular reference constraint,
Activator.CreateInstance was employed in the project.

But now when I run through in debug mode, breakpoints are ignored in the
late bound object. If I were the late bound object I would probably tell the
runtime to stick with its early-bound components and not to bother me. But I
may not be able to do so if some reflection mechanisms are keeping me on a
short leash.

thx, -greg

i know it's the obvious one, but make sure your dll's are all debug mode
with the latest source you have.


"hazz" <hazz@sonic.net> wrote in message
news:OQqPG%23meEHA.2044@TK2MSFTNGP10.phx.gbl...[color=blue]
> how do I do this? I am certain my Visual Studio .NET solution allowed me[/color]
to[color=blue]
> do this before but I don't know how the build/debug settings were
> configured.
>
> In order to get around an unavoidable circular reference constraint,
> Activator.CreateInstance was employed in the project.
>
> But now when I run through in debug mode, breakpoints are ignored in the
> late bound object. If I were the late bound object I would probably tell[/color]
the[color=blue]
> runtime to stick with its early-bound components and not to bother me. But[/color]
I[color=blue]
> may not be able to do so if some reflection mechanisms are keeping me on a
> short leash.
>
> thx, -greg
>
>
>[/color]

"hazz" <hazz@sonic.net> wrote in message
news:OQqPG%23meEHA.2044@TK2MSFTNGP10.phx.gbl...[color=blue]
> how do I do this? I am certain my Visual Studio .NET solution allowed me[/color]
to[color=blue]
> do this before but I don't know how the build/debug settings were
> configured.
>
> In order to get around an unavoidable circular reference constraint,
> Activator.CreateInstance was employed in the project.
>
> But now when I run through in debug mode, breakpoints are ignored in the
> late bound object. If I were the late bound object I would probably tell[/color]
the[color=blue]
> runtime to stick with its early-bound components and not to bother me. But[/color]
I[color=blue]
> may not be able to do so if some reflection mechanisms are keeping me on a
> short leash.[/color]

I had the same scenario happen to me after removing the reference from my
GUI project while testing. If there is not a reference to the code that
Activator.CreateInstance is calling then you will not be able to debug.

SP