Well, it could be a benefit for foxpro developers, since probably there won't be a new version for foxpro we have to deal with the fact that we will have a product that is being phased out and eventually we will have to switch to another programming language.
Now if there was a VFP.Net, even though it might not make the most sense from a technical standpoint since probably vb.net and c# are going to have some of the foxpro features; from a marketing standpoint I think it would convince A LOT of these developers to stay with microsoft and switch to vfp.net.
Now the cost/benefit of developing vfp.net to the people that are gain by having it is outside my realm.
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