>>I hope Sedna will not be tied to (or work more 'seamlessly' with) VB.Net only. I am going C# route and I'll be very very disappointed if that'll be the case.
>
>No, not to worry, Sedna will not be tied to VB.NET. Now some of the utilities we create for Sedna that are .NET related will probably be written in VB.NET, but once they are compiled, any .NET language can use them (and VFP can call them if they were built with a COM wrapper). From our latest VFP survey, around 26% of VFP developers use VS.NET as well as VFP - 13% use VB.NET and 12% use C#.

Ken, congratulations on your new approach to product development: full disclosure as you go - transparency. You will get heat but the benefit from quick feedback will be powerful. I also appreciate that MS is not leaving VFP developers in the cold but helping combine VFP and .NET.