>The argument that vfp developers need ASP.NET(or something non-vfp) to do web development is just plain wrong. I think it can be accepted that ASP.NET probably make some aspects of web development easier than using .VFP. mtdlls called from an ASP.NET/ASP stub(or using west-wind) and has a performance advantage on huge web sites, but, the argument that VFP does not have web capabilities should be thrown out at the outset. In other words, VFP continues to be an all-in-one language that is comparable, more or less, in most aspects to .NET ...

I did not mean to say that vfp developers need ASP.NET, or that VFP is not capable to build web sites.
If my words have made to understand that thing, I apologize.

But you must consider that my web team doesn't include all VFP programmers.
If your background is VFP, better you use it, but if the web designers aren't all VFP programmers, they find more useful ASP.NET.
So, I've started myself using ASP.NET and find that it does the job.

What I wanted to say in my previous post is that with .NET, C# developer and VB developer have an "universal" (let me use this word, I can't translate better) development environment which let them to build any kind of application:

1) Desktop
2) Web
3) Mobile

Why not VFP? Consider that all the world is moving to .net (Borland, ecc.)
In the old days (VFP3 - 5) VFP really was better than C or VB (let me say Encapsulation, Subclasses , Inheritance, dbf, ecc.) I would want to know if, for creating desktop applications, this gap is still there or not.

Franco