Tom,
You might want to ask Cathi and others who are more associated w/ MS and the direction of .NET, what there setup is, or if they had to use one language which they would choose. I mean, It is nice to see what Microsoft recommends, and to know the direction of .NET, but something more practical might be just to see what they use as their language of choice, or if they use both languages within one project, if they are deciding on the architecture.

Morgan

>Your point is the one we are very interested in.
>
>It is the direction that Microsoft intends and finally does take with .NET that is of interest to me. Where will C# and VB.NET be say in two years? If we read the comments from Microsoft it looks like more emphasis will be placed on the UI and IDE using VB.NET, in future releases of Visual Studio .NET.
>
>The Microsoft recommendation of using C# for classes and VB.NET for the UI seems reasonable. You can use whatever you like however, for maximum power and productivity I think I understand the plan.
>
>You can choose your route and have to be satisfied with the result. I think Microsoft is describing an “ideal” use for each of these languages but each programming environment will be a little unique. Some might follow the Microsoft recommendations of using C # and VB.NET and others may standardize on one language.
>
>Learning the framework etc. takes the real effort. It seems that whatever language you choose is not too important as it is not difficult to learn a new language as far as our group is concerned.
>
>Within our work environment we want to be able to help each other. It is critical to our company’s success. The fact that we have choices is nice but can be confusing. Standardization of one language may be our best route. Having people experienced in one or both languages (C# or VB.NET), is something that might evolve but I cannot see us standardizing on both. It is an interesting topic and we have a ways to go before we decide on our path.
>
>Our reality is this is not an academic institution. One minute of production downtime costs $36,000 and if we have a problem it is good to put all resources on it who have common knowledge. By the way we did rule out COBOL as our .NET language of choice! So we are getting close to a decision. :)
>
>Tom