RE: Possible debugger bug?
- From: jetan@xxxxxxxxxxxxxxxxxxxx ("Jeffrey Tan[MSFT]")
- Date: Tue, 11 Jul 2006 01:47:41 GMT
Hi Ben,
Thanks for your feedback!
This is because VB2005 debugger is maintained by VB.net team(cooperate with
VS debugger team), while VC#2005 debugger is maintained by C# team(also
cooperate with VS debugger team), so they have different behavior. There
are some other behaviors in IDE that are different between VB2005 and
VC#2005.
I have tried to ask why VB intentionally turned off that filter, but VB
team does not provide any other internal information. So I assume this is
based on the design of other suspect which is not public available
information. Thanks for your understanding.
Anyway, thank you for reporting this issue, I think our discussion will
benefit other community members who discovered this behavior.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
.
- References:
- RE: Possible debugger bug?
- From: "Jeffrey Tan[MSFT]"
- RE: Possible debugger bug?
- From: "Jeffrey Tan[MSFT]"
- RE: Possible debugger bug?
- From: "Jeffrey Tan[MSFT]"
- RE: Possible debugger bug?
- Prev by Date: Re: Can't debug Classic ASP In VS.NET 2005
- Next by Date: Re: Image search path for VC7.1, VC8.0, and WinDbg
- Previous by thread: RE: Possible debugger bug?
- Next by thread: bug vs2005?
- Index(es):