C# vs VB.NET in terms of tool support?

While for the most part you can generate the same MSIL, there are definitely differences in tooling. PEX, for example, works much easier with C#.

What Microsoft or 3rd party tools don't work equally well for both languages?

From stackoverflow

• I guess that answer depends on what you mean by tooling support.

  For example, when it comes to IDE support, VB does a lot more than what C# does. It just has a better IDE.

  It has extremely good background compilation and really good intellisence.

  When it comes to support for MS research projects, or "new" platforms like the XBox, VB will probably lag behind C#.

  For things done by the MS Developer Division, or Office, you should expect more or less equal support between the two languages.

  For other groups, like the MS research project you mentioned, multi language parity is often not a priority. In those cases they seem to tend to go with C# as their default choice.

  Arjan Einbu : C# has better refactoring tools in VS...

  Larsenal : Good info, but would be more useful in a list format I think.

  Ed Swangren : C# also has better intellisense. No need to Ctrl + enter to get object/method names. I don't really agree with the IDE part, but the background compilation is nice.

  Nathan W : I used to like the VB intellisense and background compilation in the IDE but since I started doing TDD it just gets in the way, so I moved to C# that + other reasons

  Joel Coehoorn : Who said you needed ctrl+enter for vb? That's just not the case.

  marco.ragogna : Intellisense for VB.NET and C# are equivalent. At least in VS2008, don't remember in previous VS versions.

  Scott Wisniewski : There are differences between them. One example is "keyword" intellisence. C# just adds keywords to the completion list. VB actually limits the keywords that are shown based on what you type. There are other differences, like with queries.

• Ektron CMS 400 is definitely more VB than C#. But if you're using Ektron, you've got bigger problems to worry about...

• Re-sharper has heaps more support for C# than VB in the code analysis side of things.

  Theres a full list here of the differences between VB and C# .NET

  Bobby Cannon : Resharper absolutely rocks. I couldn't live without it.

• One big missing for VB.NET is StyleCop I hope that they Dev Team will provide also a VB.NET version.

• Better Support for C#

  • StyleCop
  • PEX
  • Re-sharper

  Better Support for VB.NET

  • Intellisense

  (It's wiki... please add more)