>>
>>First, as you I dislike the year number names for software, but MS has W95,98, & 2000, and will have 2003. Is only Marketing and VFP need it.
>
>How will having a year make a difference?

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

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.

>
>>
>>This is true too, but next Windows will be .NET, next SQL Server will be .NET, and Why not VFP?
>>
>
>Because the next version of Windows will ship with the .NET runtime and "be the glue for .NET-connected applications". The next version of SQL Server will support stored procedures written in a .NET language.

Yes I know that.

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?

Regards,
José Luis.