BUG in debugger values.

[news.microsoft.com]

Hi,

In the debug Auto and Locals window the value that has changed becomes
highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?

Would it not be better if this window was also change highlighted?

Enum Flags INCORRECT values displauyed in debug window and intellisense.

If I have multiple bits set on an enum marked as Flags (bitfield) and have
the someBitfield = A | B, the value numeric is correct but the name shown
in the watch window and intellisense is incorrect, it is just showing A and
not A | B, this is misleading and wastes time with partially correct (and
therefore incorrect).
Thanks.

[Dmitriy Lapshin [C# / .NET MVP]]

Hi,

In the debug Auto and Locals window the value that has changed becomes
highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?
Never seen that. On my machine values in the Watch window DO become red when
they change.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

"news.microsoft.com" <di********@discussion.microsoft.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl... Hi,

In the debug Auto and Locals window the value that has changed becomes
highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?

Would it not be better if this window was also change highlighted?

Enum Flags INCORRECT values displauyed in debug window and intellisense.

If I have multiple bits set on an enum marked as Flags (bitfield) and have the someBitfield = A | B, the value numeric is correct but the name shown
in the watch window and intellisense is incorrect, it is just showing A and not A | B, this is misleading and wastes time with partially correct (and
therefore incorrect).
Thanks.

[news.microsoft.com]

The user watch window I am referring to, not the Auto or Locals tabs.

and the enums is definately a bug :D
"Dmitriy Lapshin [C# / .NET MVP]" <x-****@no-spam-please.hotpop.com> wrote
in message news:%2***************@TK2MSFTNGP09.phx.gbl...

Hi,

In the debug Auto and Locals window the value that has changed becomes
highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?
Never seen that. On my machine values in the Watch window DO become red

when they change.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

"news.microsoft.com" <di********@discussion.microsoft.com> wrote in message news:%2****************@tk2msftngp13.phx.gbl...

Hi,

In the debug Auto and Locals window the value that has changed becomes
highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?

Would it not be better if this window was also change highlighted?

Enum Flags INCORRECT values displauyed in debug window and intellisense.
If I have multiple bits set on an enum marked as Flags (bitfield) and

have

the someBitfield = A | B, the value numeric is correct but the name shown in the watch window and intellisense is incorrect, it is just showing A

and

not A | B, this is misleading and wastes time with partially correct (and therefore incorrect).
Thanks.

[Dmitriy Lapshin [C# / .NET MVP]]

> The user watch window I am referring to, not the Auto or Locals tabs.

Yes, the Watch 1, Watch 2 ... windows. I mean them too.

and the enums is definately a bug :D
Will try this out when I have some free time.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx

Bring the power of unit testing to VS .NET IDE
"news.microsoft.com" <di********@discussion.microsoft.com> wrote in message
news:e2**************@tk2msftngp13.phx.gbl... The user watch window I am referring to, not the Auto or Locals tabs.

and the enums is definately a bug :D
"Dmitriy Lapshin [C# / .NET MVP]" <x-****@no-spam-please.hotpop.com> wrote
in message news:%2***************@TK2MSFTNGP09.phx.gbl...

Hi,

In the debug Auto and Locals window the value that has changed becomes highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?

Never seen that. On my machine values in the Watch window DO become red

when

they change.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

"news.microsoft.com" <di********@discussion.microsoft.com> wrote in

message

news:%2****************@tk2msftngp13.phx.gbl...

Hi,

In the debug Auto and Locals window the value that has changed becomes highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?

Would it not be better if this window was also change highlighted?

Enum Flags INCORRECT values displauyed in debug window and intellisense.
If I have multiple bits set on an enum marked as Flags (bitfield)

and

have

the someBitfield = A | B, the value numeric is correct but the name shown in the watch window and intellisense is incorrect, it is just showing

A and

not A | B, this is misleading and wastes time with partially correct

(and therefore incorrect).
Thanks.

[[MVP] SmileSeo]

Can you make sample program for me? I will check it. I can't see that
problem on my machine.

Good luck
--

--------------------
Blogs (http://seaousak.egloos.com)
Microsoft 2002 ~ 2004 .NET MVP
"news.microsoft.com" <di********@discussion.microsoft.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi,

In the debug Auto and Locals window the value that has changed becomes
highlighted in red, BUT the Watch window does no highlighting, why the
inconsistency?

Would it not be better if this window was also change highlighted?

Enum Flags INCORRECT values displauyed in debug window and intellisense.

If I have multiple bits set on an enum marked as Flags (bitfield) and have the someBitfield = A | B, the value numeric is correct but the name shown
in the watch window and intellisense is incorrect, it is just showing A and not A | B, this is misleading and wastes time with partially correct (and
therefore incorrect).
Thanks.