I think the only one of these that's innovative enough to be of interest to nonusers of C# + VS is the DataTips. It's basically a small watch window you can pin anywhere in the code, almost like a sticky note. You can pin any number of them, anywhere in the code, and they scroll around and are visible when viewing source & debugging. They remain in place between debugging sessions (presumably stored in the VS project file). Seems extremely useful. Definitely better than setting up and tearing down watch expressions all the time.
Yup. There's so many of these that are either irresponsible (Hiding code) or of limited usefulness (IsNullOrEmpty) or too limited to be truly useful (Named Parameters).
Hiding Code: I've got an idea. If you've got to hide code, maybe it _doesn't belong in that class_. Single responsibility people.
String.IsNullOrEmpty(): Wow! Thanks MS for saving me from writing one 4 line helper method. What would be useful is if you provided these helpers for the other 90 that I need every project. Seriously, any C# dev can provide you with their "utility" project that has them.
Named Parameters & Defaults: Awesome!..... unless you need something other than a primitive, in which case you can't set default values, since it's nothing but a fancy compiler trick.
I like C#, but really, there's not much they've added since Linq that's really crazy interesting. Not that there isn't, but most of it isn't listed in this article.
Hiding code is actually quite useful - its not meant to obscure code that doesn't belong, as you imply.
Say for instance, I'm working on two methods that are expansive, but i'm trying to debug a small part of those methods. To make watching breakpoints and tracking flow easy I hide all but the necessary parts of the code.
I use regions in pretty much the same way - once I have a certain region of functionality locked down and tested, I hide it so I can focus on the part that's still being developed / tested.
My point is: If your class/code/file is so big that you need to hide code to be able to easily navigate (or worse, understand) it, you're doing something wrong.
I understand this is a religious argument of the code world and you're likely to disagree with me. I'm fine with that.
You are missing the point. Lots of large applications I work on maintaining have large awful methods. This feature is excellent in these cases.
You could argue that I should re-factor the whole thing to avoid this issue, but certain design decisions made by someone else make this a huge change, and in the world of risk adverse enterprise applications that is not going to happen.
Can you not start writing tests against those monster methods so that you've got a refactoring safety net?
I totally agree on being practical and not refactoring methods that work correctly. But if you find yourself in the monster methods making changes quite often, it seems irresponsible to not refactor and leave the camp ground cleaner for the next time you or someone else comes through it.
Its a big ball of dependencies with no chance to mock due to someone deciding on being "clever". Its up there with being untestable.
Generally I agree. If possible clean it up, but quite often its a small one line change, which needs to be fixed ASAP, so there is little chance to refactor.
To be honest, its like a matter of OCD to me - for instance, I like keeping my desktop completely free of icons (even though I don't need to).
In a similar way, I like only looking at the code that's relevant - if the method I'm working on is larger than a single screen (which happens with comments and such included) I like collapsing parts I don't care about. I don't, strictly speaking, need to in order to work effectively but I like to - as you said, more of a religious argument than a quantifiable one.
> If your class/code/file is so big that you need to hide code to be able to easily navigate (or worse, understand) it, you're doing something wrong.
Wrong. If your class/code/file is so big that you need to hide code to be able to easily navigate (or worse, understand) it, the author was doing something wrong.
The nice part about named params is that it can make your code more clear if you have a lot of parameters on a method... but you could do the same thing by introducing a parameter object and be as clear and more resistant to change.
A few of those features are ones that VB.NET developers have long been enjoying and yet VB.NET is still looked down upon when functionally it and C# have been equal for years.
Yes I'm a little bitter because I had to learn the disgustingly ugly syntax that is C# when I recently switched jobs.
If you ever need to do C++ or Java at some point, you'll have a much easier transition to those from C# than you would with VB.Net. I started with the VB 5 first in high school, then C++ & Java, and now C# where I am now.
Beware default values. They're set at the point of invocation at compile time. This isn't a problem, but you need to be aware of it. For this reason it's considered bad form to publicly use default values library assemblies - the callers won't see any change until they too are recompiled.
20 comments
[ 2.9 ms ] story [ 46.8 ms ] threadHiding Code: I've got an idea. If you've got to hide code, maybe it _doesn't belong in that class_. Single responsibility people.
String.IsNullOrEmpty(): Wow! Thanks MS for saving me from writing one 4 line helper method. What would be useful is if you provided these helpers for the other 90 that I need every project. Seriously, any C# dev can provide you with their "utility" project that has them.
Named Parameters & Defaults: Awesome!..... unless you need something other than a primitive, in which case you can't set default values, since it's nothing but a fancy compiler trick.
I like C#, but really, there's not much they've added since Linq that's really crazy interesting. Not that there isn't, but most of it isn't listed in this article.
Say for instance, I'm working on two methods that are expansive, but i'm trying to debug a small part of those methods. To make watching breakpoints and tracking flow easy I hide all but the necessary parts of the code.
I use regions in pretty much the same way - once I have a certain region of functionality locked down and tested, I hide it so I can focus on the part that's still being developed / tested.
I understand this is a religious argument of the code world and you're likely to disagree with me. I'm fine with that.
You could argue that I should re-factor the whole thing to avoid this issue, but certain design decisions made by someone else make this a huge change, and in the world of risk adverse enterprise applications that is not going to happen.
I totally agree on being practical and not refactoring methods that work correctly. But if you find yourself in the monster methods making changes quite often, it seems irresponsible to not refactor and leave the camp ground cleaner for the next time you or someone else comes through it.
Generally I agree. If possible clean it up, but quite often its a small one line change, which needs to be fixed ASAP, so there is little chance to refactor.
In a similar way, I like only looking at the code that's relevant - if the method I'm working on is larger than a single screen (which happens with comments and such included) I like collapsing parts I don't care about. I don't, strictly speaking, need to in order to work effectively but I like to - as you said, more of a religious argument than a quantifiable one.
Wrong. If your class/code/file is so big that you need to hide code to be able to easily navigate (or worse, understand) it, the author was doing something wrong.
You can use tools like this to make it right.
The nice part about named params is that it can make your code more clear if you have a lot of parameters on a method... but you could do the same thing by introducing a parameter object and be as clear and more resistant to change.
VS wise the power tools have some fun features, auto brace completion and auto semi-colon insertion when you do shift-enter from anywhere on the line.
Yes I'm a little bitter because I had to learn the disgustingly ugly syntax that is C# when I recently switched jobs.
See http://blogs.msdn.com/b/ericlippert/archive/2011/05/19/optio...