C# debugging

[VectraMan]

Is it meant to be insanely slow?

Did this first with VS2005, then I tried VS2008 which was better but still sometimes had the same problem. Doing a simple step over would take 30 seconds, and during that time it would kill Windows XP to the extent that you get the "input buffer full" system beep just moving the mouse.

Also, how the hell do you stop it from highlighting the whole line for breakpoints and current statement? It doesn't do that in C++, so it must be a C# specific setting, but I can't find it.

Grrrr. I miss C++.

[thunderlizard]

I've never experienced any undue slowness with 2005 or 2008.

[voodooflux]

Haven't experienced that either.

Seems you're not alone though: http://www.google.co.uk/search?compl...meta=&aq=f&oq=

[VectraMan]

Ta. I did find something about MDA (I think it was MDA), but the setting made no difference. I'll trawl through the rest.

Also what's with the Mickey Mouse project settings for C#? Why is it completely different to the C++ dialog in the same development environment?

I'll stop moaning now.

[PAH]

Admit it, you're a crap developer.

The breakpoint covering the whole line is a bit of a pain, always been like that. Just got to try not to write whole routines on one line. Unless you've been hoodwinked into thinking white space equals bigger libraries and executables.

[thunderlizard]

Also what's with the Mickey Mouse project settings for C#? Why is it completely different to the C++ dialog in the same development environment?

well, to paraphrase the press releases that came out with .NET 1.0:

C# is for the Developers of the Future who reject the pointery world of C++ and want a brand new start, and two (three?) fingers to tradition.

Managed C++ is begrudgingly included for Developers of the Past who fear change, and would rather have another bunch of extensions to their already over-extended barnacle-encrusted 80s throwback language, than do it the easy way.

[VectraMan]

The breakpoint covering the whole line is a bit of a pain, always been like that. Just got to try not to write whole routines on one line. Unless you've been hoodwinked into thinking white space equals bigger libraries and executables.

I don't mean the breakpoint affecting one line, just the graphical representation. In C++ you just get the nice red dot in the margin; in C# the whole line has its background colour changed. I messed with the syntax highlighting, but couldn't quite get it to work the same.

I've always quite liked VS2005, but the odd thing is that despite them seemingly only developing C# and doing nothing for C++ for the last few years, I discover in my one day at C# development the environment isn't as good for C# as it is for C++. And I'm not talking about comparing the languages, just the Visual Studio editor. At least that's my impression.

Does anybody ever use managed C++? I can't see why you'd want to. C# just isn't that different from C++ for switching languages to be a problem.

[jkoder]

Is it meant to be insanely slow?

It depends, are you debugging your app for performance issues?

[d000hg]

The C# IDE is way better than the C++ one in 2008. You don't even get any refactoring tools in C++ that I am aware of... refactoring is still a matter of copy-n-paste or find-n-replace.

[jkoder]

Glad I use Eclipse for Java, it's far superior in a lot of areas.

Not to mention it is free.