Thomas,

I agree with Mike's advice. I've heard similar rumors from some pretty reliable sources across the country that Whidbey [next release of .NET] will offer more capabilities and more RAD tools for VB.NET. MS recently released a huge resource toolkit for VB.NET. So it's starting to become clear what direction they want people to go.

Personally, I use C# for most tasks, but that's only because I used to develop in C and C++.

Let me offer the following advice...while the selection of VB.NET or C# in a multi-developer shop is important, it really is marginal compared to the following [and I'm sure you know these, but they bear repeating]...

- Learn the framework, learn the framework, learn the framework. That's where the 'beef' is, and the vast majority of it is not language-specific.

- Spend some time looking at different app tools [like Mere Mortals]

- related...take the necessary time to figure out your architecture and how you'll use the different capabilities in .NET to make it happen...how you'll handle MDI...how you want to handle reporting...how you want to handle data and updates...how you'll handle web services...etc. List goes on and on. The decisions you make in your technical architecture discussions will ultimately be more important than the language you select.

- finally, you really can use both VB and C#...as Mike said, VB.NET is great for the UI portion, and C# gives you more advanced capabilities in your other layers for class construction, delegates, etc.

Kevin