>Do you seriously think the existence of "VFP for .NET" will in the slightest way tarnish .NET? Doesn't VFP have plenty to say about the ways it can work in harmony with .NET? Does the mere mention of .NET in such close association VFP make you gag?
Why don't we name it "VFP for Linux" or "VFP for Palm"? Those names are about as relevant as naming it "VFP for .NET" since in fact VFP is not part of .NET (the fact that it can work with .NET does not mean that it's part of .NET).
Doug
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