Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Visual FoxPro News Flash
Message
From
03/05/2002 00:31:20
 
 
To
02/05/2002 23:03:40
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00647154
Message ID:
00652243
Views:
39
Since many other samples for VFP exist on the internet including here on the UT, we are not adding more samples for VFP, we are instead spending time on other efforts more valuable to VFP developers such as working to release new versions of VFP sooner than later.

The fact Visual FoxPro is not listed on the MSDN Developer Tools page is because it would just be a link to itself. I can look into fixing that if you think it is a perception problem. If you go to the VB site at http://msdn.microsoft.com/vbasic/default.asp, you will see Visual FoxPro listed in the Developer Tools list properly. The entire Visual FoxPro is going to be re-done and updated soon, it has been scheduled for a while while all the VS .NET related sites get the same update.

There were no press releases for VFP 7.0, that is why the press release page seems (and is) outdated, there was no full time product manager (me) at Microsoft when VFP 7.0 was released. There will definitely be full press releases and a bigger launch of Toledo than was for VFP 7.0.

I never said there would be no marketing. I simply stated that the more sales that occur, the more marketing budget is allocated in the future. This is true for other Microsoft products after an initial version is released, it is not unique to VFP.

If you look at the look at the UT survey results, you will see that over half the VFP developers asked say they plan to use VFP with .NET in the future, and if you look at VFP user groups all around, many topics at the meetings are on .NET. Alan Griver works in a different group than I do (VB .NET), while I work on the Fox team and the team is very busy working on the next version of VFP (Toledo). I think Toledo will be an even more exciting upgrade than VFP 7.0 was from VFP 6.0.

I never made any statements and there are no effects of Microsoft trying to move VFP developers to VB .NET. We are trying to get more VFP developers to upgrade to VFP7 who have not yet, and we will try to get people to buy and upgrade to Toledo after it is released. I hope this clarifies for you some of the items you pointed out.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform