C# breakpoint troubles in VS 2003 : Work in progress

I put my blog Contact page on a few newsgroup postings as we are seeing some strange reports of breakpoints not working in managed code. By not working I don’t mean in specific scenarios, but not working at all, under any circumstances. I am working with one particular customer who, right now, has to uninstall…

5

Windows XP Bluetooth Support : A Rant

As promised, I thought I’d rant a bit about the Bluetooth (BT) support in Windows. In the beginning there was Windows XP and it had its BT support cut before release, as the standard was very new, and I think that was the right decision at the time. Then there was XP SP1 which added…

34

Improving the reliability of the Visual Studio debugger on managed code (aka FuncEval is evil)

If the debugger hangs on you when debugging managed code (C#, VB, J#), try disabling “Allow property evaluation in variables windows“ (Tools/Options/Debugging/General). Technical Details In order for the debugger to display the value of a managed property, it has to execute that property in the debuggee, the one you are currently stopped in. This is…

6

How to Not Step Into Functions using the Visual C++ Debugger

Disclaimer: This is not a documented or supported feature. That means it was not tested, and might not work, and if it doesnt please dont call Microsoft Support and complain. If it does work, then hoorah.   Introduction Ever stepped into a function you didn’t want to? Like an ATL or MFC CString constructor for…

10

Why no C# Edit and Continue?

I received an email from Bill T. who was asking why C# wont be doing Edit & Continue (EnC as we refer to it) in VS “Whidbey”. He asked “I’ve always wondered WHY that’s so much more difficult in C#.  Perhaps you could write something in your blog describing the technical issues that make it…

35

Why the VS Debugger does not stop on first chance Access Violations (by default)

Today we got some alpha feedback about “Whidbey” regarding the debuggers default choice of exception handling for certain win32 exceptions, specifically access violation. The customer had an access violation in some native code, which ended up being caught by the COM interop layer and translated into a managed exception in his C# code. He didnt…

13

Everything isnt always Windows Fault

Everyone loves to blame Windows for, well, just about everything that goes wrong with their PC. Although I have seven PCs in my office and six in my home, I actually have few problems with Windows and seldom blame my Microsoft co-workers for my PC troubles. Just this week however I had two problems that…

1

Disabling Auto Expansions in the VS 2003 C++ debugger

This is an undocumented feature. It is not supported by Microsoft. It may change or cease to exist in future versions. Do not rely on this information. It is provided for your convenience only. If it doesnt work, please do not complain or call Microsoft support. It if does work, hoorah. In Visual Studio 2003 the…

5

How much RAM do Visual Studio developers actually have?

We have a continual battle with Marketing about how much RAM we should have on our Performance Test machines, so I would love some feedback from Visual Studio developers. Our current perf machines are Windows 2000 / 500MHz / 128M of RAM. It is my opinion that no (sane) developer is still using 128M of…

55

Introduction

My name is Andy Pennell, I am a dev lead in C#. I own the debugger and along with my team of eight developers we are responsible for the Visual Studio debugger as used by C++, C#, VB, Script and SQL. Outside of work I love messing with audio/video stuff and my home network. I…

2