John,
It appears that we are caught between the choices. If VFP is out of VS then there will be a lot of arguments about VFP not being a "real developer's tool" like VB + SQL-Server, and as you point out, MS is ignoring the desktop market by pushing VFP to play with the .NET strategy.
Of course a lot of the desktop, small business market doesn't care what the app is written in.
>Taken out of Visual Studio.....
>
>The implications of this are:
>
>1. It can get away from the scrutiny of not really being part of VS.
>2. It could be released earlier. The product is essentially complete.
>3. Acknowledges the desktop application market is worth supporting.
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