Is all that information included in your documentation? My guess would be no... How about Webconnect interop?, how about using dreamweaver with your product?

See, I can model absurdity by being absurd. You can't be expected to include all information about possible use of your product in your documentation and neither can M$.





>Not as predictable. I wish we all could be like Microsoft and do things however the heck we wanted to. Yes, I've got critical product information that allows you to use key technologies. Oh yeah, to learn it, go on over to www.relatedtechnology.com, they've got plenty of articles that will tell you what you need to know to run my product. Most likely that's a lost customer, at least in our world. There's a difference between getting supplemental info and info you need to use a product properly...
>
>>Even if it is top quality., unbiased, etc., do you really believe most developers will see it??
>>
>>The ones who are interested in managing/investing in their careers, yes.
>>
>> There's something to be said for an organized and central information repository that's accessible to all that use the product, the most logical place being the CD the product is on and updates being easily accessible thru the web or CD....
>>
>>There's also something to be said for a developer investing a little bit of time to build and maintain their own repository. (The Task Pane is a 'start'). The honus can't ALL be on Microsoft.
>>
>>I hope this wasn't too 'predictable'... ;)
>>
>>Kevin