Your opinion, as usual, is less than factual. It needs to be the best of both worlds, vfp and .NET together utilizing the strengths of both. I believe it can be so and if not, I'd rather use a hybrid (using it my own way to get the most out of it) or change to Open Source, than be force-fed this stuff
> With interop you have minimized the best of both worlds to create a hybrid with partial capabilities. If you want .Net then use .net. If you want VFP then use VFP.
>
>>My advice to you and others evaluating new techniques/technologies: I would see what interop between .NET and VFP has to offer and if that doesn't work for you, either stick with VFP as it is or investigate Open Source alternatives like PHP/Linux. I don't like the idea of being force-fed this .NET stuff either. And guess what, in 5 years if you've stuck with MS and .NET, the same cycle will likely repeat itself!