By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,068 Members | 1,073 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,068 IT Pros & Developers. It's quick & easy.

stepping through code that is late bound.

P: n/a
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

Nov 16 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
i know it's the obvious one, but make sure your dll's are all debug mode
with the latest source you have.
"hazz" <ha**@sonic.net> wrote in message
news:OQ****************@TK2MSFTNGP10.phx.gbl...
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

Nov 16 '05 #2

P: n/a
SP

"hazz" <ha**@sonic.net> wrote in message
news:OQ****************@TK2MSFTNGP10.phx.gbl...
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.


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
Nov 16 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.