But on to my two cents   I thought I may as well comment on why we are moving and state of the major reasons and benefits of C# and also point out some of the benefits of VB as well. 

Let me start by saying that I like VB.NET.  It is a good language and there are many things that I really like about it, so this is no means a blasting of VB, but rather a basic explanation of some, not all, of the reasons we have moved over to C#.

1. The design-time compiler is terribly annoying!
   
   If VB.NET would deal with design-time like C# versus constantly running the compiler within the design-time.  If a project gets very large in VB.NET, the design-time environment can't take it many times and requires the solution to be split apart.  We even had to go to the extent of removing project references at this was a major point of failure.  On an average day of development we may be kicked out of Visual Studio 5-7 times a day....way to interuppting for production.
   
2. Compiler error handling in C# is far better than VB.NET
   
   This can be a big one when it comes to reducing bugs before making it into the field.  One of our internal developers most common mistakes in VB was to forget to return a value within a function.  The VB.NET compiler may give a warning...but it will still allow it.  C# will prevent this and while talking returns, it does a better job of ensuring that all code paths have a return value when required.  Another example would be unused variables.  C# does a better job of ensuring that a declared variable is used versus VB.NET.
   
3. C# requires less code as a whole not requiring unnecessary declarative statements
   
   In this example lets take a property declaration.  In VB.NET you have to add the ReadOnly directive in order to make the property only support a get.  In C#, you just leave off a set.  Less code and easier to change later if adding a set.  While on this topic, the whole curly braces controversy generally comes up.  In truth, it really is easier to read the code without all of the extra text.  Instead of requiring End If or End Property, it is just a curly bracket.  This can fall more into opinion, but the code ultimately does look cleaner.
   
4. Inline immediate if testing
   
   Technically in VB.NET you can call Iif(...), but it is an added on method for backward compatability and very inefficient.  In C# this is a very basic inline test that is one I use all of the time.  I had to stay away from inline tests like this in VB.NET due to performance issues...but it really can improve code.  For example:
   
   
   string myVar = myTestValue == 1 ? "First" : "Second";
   
   
5. Yielded returns when returning a collection using the IEnumerator interface
   
   There is no equivelant (that I know of ) in VB.NET.  In C# there is a yield keyword that can really improve performance when enumerating a collection and returning a collection.  This is big, and can be a major improvement in regards to performance in StrataFrame when calling the GetEnumerable() method on a BO.  At present we have to create a collection and return that collection.  Using a yielded return, there is no need to create a unique collection instance for the return.  Here is a good article (http://blog.dmbcllc.com/2009/03/25/advanced-csharp-yield/).
   
6. Code editor is more RAD friendly, especially when creating new instances
   
   OK, this can be a long topic and generate a lot of debate.  But Refactoring code in C# is WAY better than VB.NET...there is not much of an argument here, natively C# is just much better.  Another super awesome feature in C# is the tab after a new statement.  C# will automatically, and always, bring up the correct class including namespace if required of the class instance being created.  For example:
   
   
   MyCompany.MyApp.MyClass class = new (TAB HERE)
   
   
   will produce this without any additional typing:
   
   
   MyCompany.MyApp.MyClass class = new MyCompany.MyApp.MyClass
   
   
   You will still have to put the parens and parms, but it saves a lot of typing.
   
7. Semi-colon terminates a statement versus having to use " _" to go to another line
   
   This doesn't sound like that big of a deal, but it has turned out to be huge for me!  I didn't realize how much additional effort was requiring to do this.  In C#, just go to the next line and keep typing.
   
8. C# doesn't require a minor if test to remain on a single line for abbreviated code
   
   For example, there are a lot of times that I may be doing a single line of code or execution after an if test.  I did this a fair amount in VB.NET but C# does it better.
   
   VB.NET
   
   Dim myReturn As String = "My Value"
   
   If !String.IsNullOrEmpty(myReturn) Then myReturn &= ":"
   
   
   C#
   
   string myReturn = "My Value";
   
   if(!string.IsNullOrEmpty(myReturn))
        myReturn += ":";
   
   
   The nice thing in C# is that you can do it on the same line if you want to.
   
9. C# is the industry standard and the primary language of Microsoft
   
   This is a good reason that C# has a tendency to do more than VB.NET and the editor and RAD tools are better...it gets the most attention.  I am in no way talking negatively about the VB.NET team...they are awesome, but C# lends itself to a little more flexibility for this reason alone.
   
10. Can compile an application to run on other operating systems
    
    This is not a major reason, as I am not insane enough to write for another operating system like Mac....in fact, I was at Best Buy the other day and had to wash my hands after I touched a Mac!   But the point I am making here is that you have more control with the compiler which in and of itself can play benefits downstream....but this is no reason to choose C# over VB.NET.
    
11. Documentation is actually slightly better in C#
    
    C# does a better job with commenting and documentation.  It is also, by default, better about throwing warnings about any public piece of code not commented.
    
12. Easier to tie into the API
    
    In C# there are many times that you can get directly to the API versus having to call a bunch of Declare statements.  Minor, but nice.

I could actually give a number of other examples, but my family is trying to get my attention to head to church!   At any rate, I am sure this thread will grow some more and I will post more examples at a later date, but I thought this might help.

The editor is actually far better once you get used to it and get it setup.  I might recommend getting CodeRush from DevExpress.  It is horriblly irritating with VB.NET, but works very well with C#.  You can make the text editor look a lot better, change how regions looks, colors, etc.  And it makes moving to C# a lot easier.  You will have to turn off a lot of irritating junk that is enabled by default, like templates...they REALLY annoyed me.  But once you get it setup and configured to your liking, it is much better.

But before you haul off and get that, the settings you are talking about are standard .NET options.  Click on Tools -> Options and go to the Text Editor options for C#.

All of the frustrations you mentioned can be fixed here.  You might add a frustration or two while figuring it out also

LOL...the Ctrl K+D is something I use a lot...a whole lot.  The ONLY reason it will not work is if there is an error within the syntax...or you have your formatting setup to do just what you mentioned. 

I am not generally a big fan of too many tools, but CodeRush from DevExpress is really a nice Add-In for VS and makes formatting code, snippets, etc. really nice.  You can move methods around between regions, change declaration types, etc. with inline editor tools (if turned on) through this add-on.  Check it out, it really is nice for C#.  I will tell you this, however, if you leave it on for VB.NET....well...prepare for a few cuss words to pop out of your mouth.