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

vb data breakpoint?

P: n/a
I understand the VS2005 still doesn't support data breakpoints in VB. My
question is this.. does anybody know of a 3rd party product that DOES
support data breakpoints in VB?

As an aside, does anyone know why it seems to be so hard to impliment data
breakpoints in VB? It is such a valuable tool.

Thanks
Oct 10 '07 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Are you talking about setting a breakpoint and then setting its properties
to conditional so that it only breaks when a particular value changes?
"JohnR" <Jo******@hotmail.comwrote in message
news:4V5Pi.4340$d2.2000@trnddc08...
>I understand the VS2005 still doesn't support data breakpoints in VB. My
question is this.. does anybody know of a 3rd party product that DOES
support data breakpoints in VB?

As an aside, does anyone know why it seems to be so hard to impliment data
breakpoints in VB? It is such a valuable tool.

Thanks

Oct 10 '07 #2

P: n/a
On Oct 10, 12:17 pm, "Scott M." <s-...@nospam.nospamwrote:
Are you talking about setting a breakpoint and then setting its properties
to conditional so that it only breaks when a particular value changes?

"JohnR" <JohnR...@hotmail.comwrote in message

news:4V5Pi.4340$d2.2000@trnddc08...
I understand the VS2005 still doesn't support data breakpoints in VB. My
question is this.. does anybody know of a 3rd party product that DOES
support data breakpoints in VB?
As an aside, does anyone know why it seems to be so hard to impliment data
breakpoints in VB? It is such a valuable tool.
Thanks
Data breakpoints are designed to break at any point in project. The
conditional breakpoints only will break on a certain line if the value
has changed, and not on any line the value changed. Essentially, a
data breakpoint is like a conditional breakpoint on every line in the
project.

As far as support goes, the only time that data breakpoints are
available are when writing native code, presumably in C++. I believe I
read somewhere this is because the managed Garbage Collector would
make true data breakpoints impossible (or at least super-hard) to
implement. Although I haven't looked at the Orcas betas yet, it's
possible they have added them in, but I wouldn't bet on it.

Thanks,

Seth Rowe

Oct 10 '07 #3

P: n/a
On Oct 10, 10:38 am, rowe_newsgroups <rowe_em...@yahoo.comwrote:
On Oct 10, 12:17 pm, "Scott M." <s-...@nospam.nospamwrote:
Are you talking about setting a breakpoint and then setting its properties
to conditional so that it only breaks when a particular value changes?
"JohnR" <JohnR...@hotmail.comwrote in message
news:4V5Pi.4340$d2.2000@trnddc08...
>I understand the VS2005 still doesn't support data breakpoints in VB. My
>question is this.. does anybody know of a 3rd party product that DOES
>support data breakpoints in VB?
As an aside, does anyone know why it seems to be so hard to impliment data
breakpoints in VB? It is such a valuable tool.
Thanks

Data breakpoints are designed to break at any point in project. The
conditional breakpoints only will break on a certain line if the value
has changed, and not on any line the value changed. Essentially, a
data breakpoint is like a conditional breakpoint on every line in the
project.

As far as support goes, the only time that data breakpoints are
available are when writing native code, presumably in C++. I believe I
read somewhere this is because the managed Garbage Collector would
make true data breakpoints impossible (or at least super-hard) to
implement. Although I haven't looked at the Orcas betas yet, it's
possible they have added them in, but I wouldn't bet on it.

Thanks,

Seth Rowe
While not ideal... A work around for this is to NEVER access your
variables directly. Always wrap them in a property - even if it's
private. Then you can set a breakpoint in the setter of the property,
and bling you break everytime something sets the property. Yes, it
means that you have to be a little disiplined in your codeing - but it
does give you a sort of solution :)

--
Tom Shelton

Oct 10 '07 #4

P: n/a
Hi Tom,

Now that's an innovative solution! I never thought of it... You
actually don't even have to be disciplined, you can temporarily create a
property on the fly when you need to track down a data breakpoint. Thanks
for a great tip.
"Tom Shelton" <to*********@comcast.netwrote in message
news:11**********************@o3g2000hsb.googlegro ups.com...
On Oct 10, 10:38 am, rowe_newsgroups <rowe_em...@yahoo.comwrote:
>On Oct 10, 12:17 pm, "Scott M." <s-...@nospam.nospamwrote:
Are you talking about setting a breakpoint and then setting its
properties
to conditional so that it only breaks when a particular value changes?
"JohnR" <JohnR...@hotmail.comwrote in message
>news:4V5Pi.4340$d2.2000@trnddc08...
>I understand the VS2005 still doesn't support data breakpoints in VB.
My
question is this.. does anybody know of a 3rd party product that DOES
support data breakpoints in VB?
As an aside, does anyone know why it seems to be so hard to impliment
data
breakpoints in VB? It is such a valuable tool.
Thanks

Data breakpoints are designed to break at any point in project. The
conditional breakpoints only will break on a certain line if the value
has changed, and not on any line the value changed. Essentially, a
data breakpoint is like a conditional breakpoint on every line in the
project.

As far as support goes, the only time that data breakpoints are
available are when writing native code, presumably in C++. I believe I
read somewhere this is because the managed Garbage Collector would
make true data breakpoints impossible (or at least super-hard) to
implement. Although I haven't looked at the Orcas betas yet, it's
possible they have added them in, but I wouldn't bet on it.

Thanks,

Seth Rowe

While not ideal... A work around for this is to NEVER access your
variables directly. Always wrap them in a property - even if it's
private. Then you can set a breakpoint in the setter of the property,
and bling you break everytime something sets the property. Yes, it
means that you have to be a little disiplined in your codeing - but it
does give you a sort of solution :)

--
Tom Shelton

Oct 11 '07 #5

This discussion thread is closed

Replies have been disabled for this discussion.