G
Guest
Hi Bill,
Yes, but why then the error only appears when WD is here. Did it enforce
some "standard" ?
n`Ahu
I've heard various explanations--it seems to be some form of "dll hell" type
conflict, but I don't understand it yet. I don't know whether it is
"windows defender's fault"--or whether the other app involved has failed to
follow some particular standard, or whether there's something unclear in
recommended .NET programming practices, and it is just now becoming visible.
Yes, but why then the error only appears when WD is here. Did it enforce
some "standard" ?
n`Ahu