Simple but Interesting Features of VS2010 and C# 4.0

http://www.codeproject.com/KB/cs/VS2010InterestingFeatures.aspx

by yread • 15 years ago

29 20 15 years ago

numlocked• 15 years ago

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.

mendicant3• 15 years ago

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.

varunsrin2• 15 years ago

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.

kevinkemp2• 15 years ago

I wouldn't lump named parameters and defaults together like that. They're completely separate concepts.

mattmanser• 15 years ago

Yeah, 3.5 was where all the c# innovations were, .net 4 seems to have been all about the DLR.

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.

aforty• 15 years ago

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.

nopassrecover• 15 years ago

The "ugly" c-style C# syntax is far more expressive. Using VB.NET feels like using crayons to draw portraits.

artmageddon• 15 years ago

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.

kogir• 15 years ago

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.

See http://blogs.msdn.com/b/ericlippert/archive/2011/05/19/optio...

xpaulbettsx• 15 years ago

Interesting, didn't know that - good tip

photon137• 15 years ago

Isn't that a standard feature of x86 function-invocation, ie, argument values are stored in caller's stack? (although C# runs on CLR, but still...)

Simple but Interesting Features of VS2010 and C# 4.0

Related Stories