One of the selling points for .NET is that a team of programmers can choose any combination of .NET languages to deliver a project.

The major point that was kept out of the M$ marketting machine is that .NET is memory hungry (~27 MB for each instance of a running application, ~40 MB for a group of Web Services) and requires a minimum PII 450 MHz processor. If memory and processing power are not an issue, then I see no problems with .NET


>>Our shop is looking at migrating away from Visual FoxPro and we are getting a lot of confusing information right now. How come consultants like Victor Campos are recommending C# over VB.Net? They seem to think that this is the only language with any future. Victor says C# is the better object oriented language with the better syntax and capabilities.
>>
>>
>>Is this correct and what language is best? Can anybody offer any help here?
>
>Hi William,
>
>The last time we looked at migrating from VFP, we were pretty disappointed with the abilities of the other languages to quickly create a reliable app (granted .net was not out at the time). We finally gave up on VB, and picked up a VFP framework instead.
>
>
>Recently we've been using VFE, and have found it extremely fast to develop in. It takes a ton of the tedium out, and puts a lot of stability in. Also, I just took a class in using VFE to develop SQL 2000 apps, and it is WAY COOL!!!
>
>If you've been writing for any amount of time in VFP, you might give one of the frameworks a try, before you dump all your experience, and go for another language...
>
>Good luck.
>
>Daniel