From the letter: "Our goal now that the Visual FoxPro Roadmap is released is that there won't be anything that insiders know that members in the Visual FoxPro community won't know. We want to expose all that Microsoft is planning, thinking, doing, etc. (transparency) around Visual FoxPro long term so there are nothing to assume or guess."


I realize that you and the the team probably put a good deal of thought into the letter and road map before posting them and I appreciate the effort. In the interests of transparency as to planning, thinking, and doing...

Could you please expound on the work that is being done in Sedna? I would like to know if it is a collection of .NET assemblies, a collection VFP classes, both, or something entirely different?

How will Sedna differ from what can already be accomplished by using COM Interop and a little elbow grease?

What VFP 9 reporting enhancements are currently being worked on or considered?

What specific areas of .NET and VFP, if any, should be focused on for VFP developers to "hit the ground running" when Sedna is released?

Will we be able to leverage Avalon, XAML, Indigo, and/or WINFX in some capacity using Sedna?

In addition to VFP 9, will additional develoepr tools be needed in order to use Sedna? Such as Visual Studio 2005, certain SDKs, etc.?

Those are my top questions and probably of some interest to other members of the VFP Community. Any answers to the above would be appreciated and extremely useful as I position my company and the applications we create for the future. I believe the above questions are also in keeping with your ultimate goal of transparency. Thank you.