As a customer I second that demand.

I'd like to have such examples in the docs.

>Speaking from a customer standpoint again, I specifically would expect that a product that claims to "create solutions for the desktop and web" and has a "strong story" for .NET interop to be able to show me, after I purchase the product, how to create web apps (remember you said FOXISAPI is no longer supported and will no longer be included) and how to do vfp .NEt interop. If you can explain to me how that's shown to the developer who has just purchased vfp9, by whatever method, I'll be satisfied. I think everybody would agree that this shouldn't involve googling at all...
>
>>>As specific as I can be, you should put those best examples in the documentation so developers have easy access to it. You could even call it a new feature to help sell the product...
>>
>>You haven't given any specifics for examples or content needed that do not already exist. I already explained our way of documenting the product and putting samples online, this is not going to change. We do not use product documentation as a way to market a product. The only way for someone to see the documentation before they upgrade or buy the product is to go online, to the same page where there are many links, content, and examples online already.