>
>What can C# do for the user that Visual Fox cannot?

VFP cannot create managed code that executes directly within the .NET Runtime. Right now this is not a problem because not very many people have the .NET Runtime installed on their desktops. Future version of Windows will have it installed by default.

You have to imagine the future when all desktops will have the runtime installed. Applications will be deployed by downloading components off the corporate intranet or the internet.

COM components built in VFP don't work very well in this type of environment because of the registration and versioning problems (DLL Hell). .NET is supposed to fix all that. The jury is still out.

I hope you see that .NET will not just be for ASP.NET and web services. It will also be positioned for the desktop. Through Web forms you can create smartclient front ends for web services that give the user a richer experience than they would get from a browser.

Again, right now there is no problem. Create your business logic in COM components and .NET can access them through COM Interop. But keep an eye on where Microsoft is trying to go with all this stuff.

-Dave

>
>What are some of the immediate or more noticable, advantages to using C# over Visual Fox?
>