Yeah I can hear it now from those C# devs. Why would I ever code in VB? Well, you just never know. Maybe you'll get an awesome job where the company is already vested in VB. Maybe you'll want to use LINQ to XML. Whatever the reason, while my favorite OReilly Pocket Reference (C# & VB.NET Conversion) is a must have, there's a new resource that is not to be missed.

Kathleen Dollard is building a list of "What a C# Code Should Know Before They Write VB" over on her blog, Leaning into Windows.

Kathleen knows VB intimately and has had a lot of impact on how the language looks today (and how it will look tomorrow).

She also does a lot of work in C#.

Here list not "how to read VB samples and interpret them into your native tongue." It's really about sitting down and writing VB code.

This list is intended for people actually building projects in VB. The framework is so core to what we do that it doesn't make sense to demand one language or another. But if our crossing over in either direction it makes sense to embrace the elegance of the language you're going to work in and to understand its nuances.

There are not a lot of great C# coders who have a deep understanding of VB, so Kathleen is uniquely qualified as one of the few people who I would trust to get this advice from.