>
But this would imply also that VFP has no place in an n-tier application, or inside the .Net plattform, what is not true.
<

I don't think so. n-tier apps existed before Dot Net. And, there are other tools that will work with Dot Net that do not ship in the Dot Net Box.


<
Even people from MS that doesn't know much about VFP (most of them) bought on the argument that VFP is excelletn for middle tier components.
>

This is a statement of fact that I agree with...

>
Wouldn't this "Desktop App" strategy conflict with the market development of such applications as WebConnection based sites or Enterprise solutions?
>

If anything, it helps the market space that web-connect solutions occupy.


>
My current argument for those who ask about VFP not being in the CLR is that VFP is not a language at all, but a development environment that can't be reduced to the CLR. And that it is important enough for MS to stand side to side with the rest of the tools (i.e: it deserves its own icon in the VS startup).
>

Interesting point..