Tracy,
I would say documentation is always the first place developers look. One of the reasons is that it's how MS says it should work. There may be 10 different ways of doing it in magazine articles, all good, but I think MS is expected to have a best practices in the docs, at least for important technologies like .NET interop which will let developers use the strengths of both .NET and VFP. I think the comparison with using VFP with MS-WORD is a good one. There's an explanation in the help docs for that along with links to examples...

>I'm in agreement with you on this one. The majority of VFP developers I know do not use the web on a regular basis to locate 'how to' articles in VFP -- basically because they work for corporations that limit their web usage for a variety of reasons. However, they do in fact read the documentation and magazines.
>
>
>>>>Pretty simple - Claude has a vested intererst... <g>
>>>>
>>>>All that aside I don't think it would be a bad idea to have those samples in the help file even if they are simple. It would be useful to show how to create a COM object and consume it in ASP and ASP.NET and a Web Service. This is after MS's primary Web platform and not exactly rocket science to incorporate. yes, there will be more detail required beyond a simple one pager, but it's a good place to start.
>>>>
>>>>This shouldn't be a white paper style thing but simple examples of a short page or so. You could then point the docs to the White Paper on MSDN page or other resources like the Task Pane that would provide further info. Even better if you had links that point to MSDN articles or whereever directly (I'll certainly volunteer my articles if you need them <g>, but I think there's already 'sanctioned' content on MSDN along the same lines.)
>>>>
>>>>Web Development is certainly high on the list of things developers will need to do with Visual FoxPro or otherwise.
>>>
>>>We have links to the VFP web site on MSDN in the docs, and even on the Help menu of the VFP system menu called Visual FoxPro on the Web. It would seem that most every developer doing web type development would launch that menu item, or view the Task Pane contents, or go to the VFP web page manually. Traffic on the VFP web site is high every month. We don't link to "specific" whitepapers online in the VFP docs since over years time, they might be outdated or new ones may be released with more updated information, etc.
>>
>>Newsflash: Documentation gets outdated <g>... What do you think happens to a CHM file?
>>
>>At least on a Web link the content can be updated or redirected to something more current.
>>
>>I just think that making people dig for this information is potentially a lot of work when you can have a simple link. This won't apply to people who hang out in places like this, but for those that are in their little development bubble and don't usually 'do online research'. I think that is a larger segment than you might give credit to... I know I deal with a lot of these people on a regular basis...
>>
>>
>>
>>+++ Rick ---