I was going through Mark Michaelis’ MSDN article on Team Test and ran into a problem executing the first demo. My test would always abort do to a Script Blocking exception reported from my Microsoft AnitSpyware tool. It appears that Team Test generates a batch script file under {USERPROFILE}\Local Settings\Application Data\VSEqtDeploymentRoot and attempts to execute it. This is where the AnitSpyware tool jumps in and says “I don’t think so…” and causes the test to abort.
This issue has already been documented as a bug and the reported workaround is to “temporarily disable AntiSpyware software” (?!?!) but I felt a better (but not perfect) answer is to just disable the Script Blocking component in AntiSpyware. To do this, open Microsoft AntiSpyware and select Real-time Protection from the upper-right panel. On the Real-time Protection screen select Application Agents, than scroll down to Script Blocking in the Application Agent Checkpoints list and Deactivate it.
Hopefully this will be resolved in time for the production release.
April 28, 2005 at 05:55
Strange, i thought i was the only one with this problem! Thanks for the information. Kept having to disable Antispyware which I always forgot to do after logging in again. Very frustrating.
Thanks.