Morgan,

What I am experiencing when working with some large sized companies is that they have entirely seperate teams that handle the UI and a different team that handles the middle-tier. The focus and functionality of these teams are very different. Most of the people on the UI team have experience with Visual Basic 6. They are more comfortable with using VB.NET for future work. The team leads like the RAD focus of VB.NET and future direction that Microsoft is taking with VB.NET. The middle-tier developers are mostly C++ developers, who primary concern is performance. The team leads are choosing C# for their development language. The future plans for C# work very well into the needs these developers are wanting.

This said, I do discuss with the project leads about the pluses and minuses of using multiple languages in their application when I consult with them. Some companies have a philosophy of using only one language and others feel that the added productivity of the skill sets and focuses of the different languages out weights any negatives.

>>Hi Morgan,
>>
>>You might be surprised to find out the number of large enterprise-sized companies that using both VB.NET and C#. The main use of VB.NET is for the UI portion of the app and everything else in C#. There are many clients of mine that are doing this very approach because of the skill base of the developers involved. The focus of the languages are very different and will be even more so in the future.
>>
>
>I wouldn't doubt that a lot of large enterprise-sized companies are using both VB.NET and C#, but it seems like another layer of possible confusion to add. I mean, if there are both skill levels for developers, and that is the beauty of .NET. But, ideally I would think that it would be better to keep to as few of languages as possible. I mean, if I would need to bring some back-end developers to a UI part of the application because time restrictions. I just think it adds another level of potential problems.
>
>Morgan