Mahlzeit,
hier 'ne Kleinigkeit zu lesen ;-)
https://msdn.microsoft.com/vfoxpro/roadmap/
https://msdn.microsoft.com/vfoxpro/letters/
https://www.craigberntson.com/archives/2005_06_01_archive.asp#111764598359410031
Tja, dafür, dass er alles offenlegen will, ist die Roadmap wirklich sehr dünn.
Im Universalthread ist Ken etwas offener. Hier ein paar Auschnitte aus Messages von Ken von gestern und heute im UT:
Thanks for the feedback. I just did a video interview in my office by Robert Scoble for Channel 9 showing some new features we are planning to include in Sedna and demos of VFP working with .NET and VS 2005, as well as Avalon (XAML). It is all a very early sneak preview of the type of things we are working on. And although it is an early start, the demos are pretty exciting. I'll have this video go online in mid June for anyone to watch (including non-VFP developers). And while it is a start, it is only the beginning since we just started on Sedna and won't go full speed on it until July. Some of the demos relate to new IntelliSense features, new report system features beyond what is in VFP 9.0, and lots of cool interop with .NET. Stay tuned. :)
Exactly, as .NET becomes the primary Microsoft platform for application development long term. It is much like creating a Windows version of FoxPro last decade, going from DOS to Windows. We are working on things to help VFP developers, businesses using VFP applications, etc. for the long term (second half of this decade and into the next).
Our focus and resources are going into enhancing VFP for interoperabiilty, not the core VFP product beyond what is needed to enhance and deliver on the interop story. Leveraging the .NET Framework, features for running VFP apps on Longhorn, being able to call Avalon forms from VFP, working with SQL Server and Office better, etc. are all a higher priority than adding new features to the grid and other controls, etc. We will enhance many of the IDE features in VFP via extensiblity. Lots can be done here, more than some might expect or imagine. That includes new DLLs written in C++ and not just Xbase (FoxPro) code.
Yeah, and the time and effort (costs) of adding IDE things to VFP is not as important has how VFP apps deploy (the end user experience). The runtime (end result) is what is more important than nice features. Keep in mind that the VFP team now (and with VFP 9.0) is under 10 people while people working on VS 2005 and the .NET Framework is well over 1000.
Ich schließe mich weitgehend der Meinung von Craig Berntson an. Die Road zu .net ist für mich, zumindest aus heutiger Sicht, kein Weg. Mal sehen, ob Ken mich von etwas anderem überzeugen kann. :-)
Bis denne, JoKi
