General information
Category:
Visual FoxPro and .NET
I sorely miss the command window and prototyping tools. Much longer to do crap in .NET
IMO, MS dumpin on and dumping COM is mostly FUD because it's a power play (maybe a slight technical advantage). There's nothing inherently wrong with COM. And COM in Windows is better than stuff like PHP on Windows which Microsoft is furiously back-pedaling to be like because it's so easy and popular.
>I have to say that the further I get into .NET 4.0 ( the VFP 6.0 of .NET <g> ) the more I "get" why the strategy to move from COM and GDI made good sense. I think what a lot of our Fox community misses is that there were a lot of reasons besides its imminent demise why many top level Fox developers migrated to .NET over the last ten years. I'd be interested to know how former successful VFP developers who have made the transition to successful .NET developers would feel about going back to the VFP paradigm even if VFP were a supported product at MS.
>You're mistaken that VFP was discontinued because Microsoft saw it as a strong competitor to .NET. There are two reasons. 1) VFP sales were declining and VFP either had or was close to the point where sales did not cover expenses of continued development. 2) DevDiv made the decision that COM-based tools were not the future. It was .NET. Therefore, VFP did not fit.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only