My previous employer removed it from 15,000 workstations. Bet you can't guess who that was! Hence my many posts in the past on APIs :o)
>The biggest problem I see with WSH is that some IT departments disable it (or don't allow it to be installed) on user's pc's due to security concerns. I find that using API's in all cases gives far less problems overall.
>
>Alan
>
>>Hi David,
>>
>>WHS wraps API calls with OOP interface. Always it hides complexities of managing input and output parameters and calls.
>>
>>Whenever possible try to use WSH.
>>
>>Possible issues against WHS:
>>- sometimes installed WSH version is old to support certain functionality
>>- API covers much more larger areas than WHS
>>- sometimes API calls give more control over the process
>>
>>Also WHS has bigger overheads comparing to API, though it's hardly important.
.·*´¨)
.·`TCH
(..·*
010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
