You, and those who made the decision to make things very clear, did a great job. Letting the MVP's blog the information from the Summit was useful, as we had information coming from multiple sources. Thanks for your efforts in this, and thanks for the VFP team's efforts in making VS a workable environment relative to the fine-tuned, developer-friendly environment we have had in VFP. I can understand the anguish in the community; but those of us who looked up Sedna (a dark, lonely solar satellite that might or might not be a planet, at the very edge of the solar system) when it was announced, had taken the hint, and experienced the anguish: any other decision would have been a (delightful) surprise.

Now, if IronPython were to become a full-fledged member of VS... <s>

Hank

>Not sure how to answer this. We've said for years that VFP wasn't a strategic product. We said that one reason I owned VS Data was to get the VS team (and particularly VB) understand VFP and vice verse. We said that we were working on LINQ as well as Sedna.
>
>That said, there was no decision to end VFP core enhancements until fairly recently. As part of that discussion, we decided to open source Sedna at no charge. After that decision, the next question was "should we tell folks"? Note that not many companies do that so openly. The team's reaction was "of course we should" and we stuck to that thru a number of discussions. The next question was when and how do we tell people? With the MVP summit coming up, I felt that telling them in person was the right thing to do. So we hurried to get everything in place (and there's a lot to get in place so we can answer questions about support, the MVP program, etc.). Basically, I've been working over 100 hours a week the past few weeks. I give props to my current manager, Sandy, for letting me put aside much of my regular work to focus on this for a few weeks less than a month before we release four products that I've architected to beta.
>
>I hope that helps.
>
>yag
>