>What are other people's experiences with upgrading 'legacy' FoxPro (FP and VFP) to VB and VB.NET and C#.NET? Be honest now.... successes or sorrows???
>
>(Mine has been that at the places it has been attempted, they stayed with the Fox.)

If one were to stop and consider that .NET is more or less Microsoft's spin on implementing "Web Services", that you don't really need .NET to create Web Services, that other Vendors (Sun, IBM) are able to provide and consume Web Services without .NET, that Microsoft itself admits that certain organizations will never (fully) adopt VB.NET or C# because they can be more productive in their current language of choice (eg. Wall Street and APL), that Web Services is mostly about SOAP (which any COM enabled language can deal with), then one can see that rushing to "upgrade" to .NET isn't that big a priority.

Most of the .NET evangelists here seem to be making this an "Either/Or" proposition; it's not.

Learning how to "architect" the use of Web Services using a variety of tools (to suit the User/Customer/Application) is more important (IMO) than simply "learning .NET".