Hi,
Has anyone else experienced weird errors after installing SP1?

These 2 are starting to really get on my nerves:


1) If i have a watch set on an expression rather than a variable, when
i launch a debugging session the watch window flickers and the program
takes ages to launch (due to the CPU being hammered by the ID watch
window!), even if the expression is out of scope.


2) The worst, again with the watch window. I have an inherited class
(Tokenizer) that has a public property _Token defined in the base
class. If i enter 'Tokenizer' into the watch window, and open the
treeview up to view the _Token member, i get a different result than if

i enter Tokenizer._Token. The _Token property is not overriden in the
inherited class. eh? that's what i thought.


Help!


James Randle.

Also posted in microsoft . public . vstudio . development, but as i am
using c# i thought my c-sharpian colleagues may have come accross the
same problems :0).

Errr, found out what was going on ...

One of my other properties contained a piece of code which reset the
tokenizer to the beginning of the string. When the debugger queried
this property, it reset the tokenizer.
I would like to blame MS but, alas, it's my fault. I'm sure it wont be
the last time.

James 'my fault' Randle.


pigeonrandle wrote:
> Hi,
> Has anyone else experienced weird errors after installing SP1?
>
> These 2 are starting to really get on my nerves:
>
>
> 1) If i have a watch set on an expression rather than a variable, when
> i launch a debugging session the watch window flickers and the program
> takes ages to launch (due to the CPU being hammered by the ID watch
> window!), even if the expression is out of scope.
>
>
> 2) The worst, again with the watch window. I have an inherited class
> (Tokenizer) that has a public property _Token defined in the base
> class. If i enter 'Tokenizer' into the watch window, and open the
> treeview up to view the _Token member, i get a different result than if
>
> i enter Tokenizer._Token. The _Token property is not overriden in the
> inherited class. eh? that's what i thought.
>
>
> Help!
>
>
> James Randle.
>
> Also posted in microsoft . public . vstudio . development, but as i am
> using c# i thought my c-sharpian colleagues may have come accross the
> same problems :0).