>Well, Ken, since you ask, some of us were hoping that Microsoft would give more convincing signs that it has been sincere in its assurances to the VFP community. You and Steve Ballmer have gone to such lengths to tell us about the many ways that VFP 7.0 and .NET can work together, and VFP was, after all, a piece of Visual Studio 6.0. Is it so far-fetched to imagine that a single VSNET newsgroup might be devoted to the topic of VFP 7 interoperability with .NET? Is VS.NET so fragile that the least mention of VFP in that context would damage it?

Having a VFP newsgroup under VSNET is confusing to most people, many people have asked if VFP is part of VSNET after seeing those newsgroups, we need to remove them to avoid the confusion. Most VFP developers wanting to talk about .NET just go directly to the .NET/VSNET newsgroups because that is where the community for .NET is. If you think a .vfp.dotnet newsgroup (under the VFP newsgroup sections) is needed, let me know what you think, it can be considered, but I don't see the demand there at this time. For example, since the .NET Forum as started here on the UT, the .NET discussions on the FoxForum have almost disappeared since VFP developers who want to talk about .NET go to the .NET Forum and not the FoxForum.