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?
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?
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.
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
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#
Better Support for VB.NET
(It's wiki... please add more)