Microsoft publish a public Enterprise Localization Toolkit for .NET. Is VFP a stepchild?

Ken Levy remembrance about VFP localization toolkit some deals. Why .NET developers don't need any deal? A lot of application support localization tables. VFP must support that too.
When Delphi programmers see my page setup dialog and print preview toolbar and say "These are in English. Can't you translate them to Turkish. Heh hehe" that do me angry. But I cannot said anything. Because VFP don't let me.

Microsoft want to developers use .NET. So do everything to use developers use .NET.
I don't use .NET!.. I use VFP. IF I change that I'll use Delphi. Do you okey Microsoft!..