>>Yeah, a name change could only help. How about VisualData++ or Visualkickbutt?
>>I can't believe so many seemingly intelligent people want to pull VFP from .net. MS will never spend money to market VFP. At least by leaving it in the suite, we get some exposure and can say we are in the product.
>
>I still like my Visual Phoenix suggestion from a couple of years ago.
>
>The one point that Mike made in his Wiki doc that has stayed with me is that VS is now one tool rather than a suite. Except for VFP. I don't want to see it taken out because I really think that will be the end of the product but it really doesn't fit anymore.
>
>A better strategy from our POV would be to make the next rev incremental for everything but VFP. They polish C, C# and VB. VFP gets overhauled so that we are a part of the IDE and can use the CLR. You'll hear screams from everyone about loss of functionality but it's definitely the best thing for the product. Again, don't think there is any way this will ever happen.
>
>Just my opinion

Well, if we get CLR we lose the functionality of VFP. It doesn't make sense from MS's standpoint either. It is well known that perception is reality, so given that, if it stays in .net it is still a viable product. Pull it and who knows how long before we're relegated to VB or Delphi or X! This seems so clear to me, but then again I'm a trained observer!*g*