>In Marketing there is a thing called ideas association, then:

Yup.. and when MS added .NET to everything, it caused lots of confusion. Talk to anyone that used Clipper, Summer 87 and ask them about the confusion and problems they had when using a date with the product version. That's one reason the next version of Clipper was 5.0.

>
>Windows.NET 2003
>SQL Server.NET 2003
>VS.NET 2003
>VisualFoxpro.NET
>
>8-? Something wrong in this series...
>
>VisualFoxpro.NET 2003.
>
>8-D Ok, all is Ok.
>
>We know Visual Foxpro 7.0 don´t need SOAP for work, but we have into VFP7 CD, and a Link for install it, because VFP7 is good for Web Services and SOAP is needed for Web Services. Ok. VisualFoxpro.NET 2003 (aka Visual Foxpro 8.0) don´t need .Net Framework for work, but we know VFP8 work so well with .NET, then add a link to VFP8 Instalation for Install .NET Framework, and include it into VFP8 CD.
>
>You and me know is only marketing, VFP8 is the same, called VFP8 or VFP.NET, but all us is demand MS for Marketing VFP year after year, we can up the .NET Marketing Train, Why not?
>

For the reasons I've already mentioned. MS already started adding .NET to everything and it just caused lots of confusion.