“I have virus protection software X with Y features enabled and I’m trying to get
Visual Studio to do Z but I see error messages instead. What
can I do?”
I see this question a LOT about Visual Studio .NET 2002 and 2003. This
post is an effort to consolidate the answers to these general issues into one location.
Why do these problems exist?
What are the common problems and what can
I do about them?
Don’t run script blocking software during
the install of Visual Studio. If
you did, ignored warning messages during the install, and you’ve had problems with
VS from the first launch there isn’t much you can do but re-install VS. Covered
KB article. For Whidbey we’ll be moving the install away from its reliance on
scripting thus avoiding this issue.
Other Script Blocking Issues: If you got
past the install of VS, but have re-enabled most of the popular script blockers you
may encounter problems that you will need to turn off script blocking to solve. These
problems may not even give you warnings and may just manifest themselves by just shutting
down VS when a user attempts the following.
The problem with turning off script blocking completely is that there are useful reasons
to enable script blocking. If your AV
software allows you to be selective you should try to allow the devenv.exe process
to run unfettered and ignore warnings from “VS://” URLs.
Real Time Scan Issues: Virus Scanning
software enabled for “Real-Time” scanning can dramatically effect performance and
sometimes cause apparent hangs during the following operations listed below. The only
solution is to disable the real time scan. Some real time scanners will let you tell
them to ignore files in certain locations which might be a more secure option.
Other Random Issues:
If I find more issues I’ll post them here as well. If
you have run into other similar issues feel free to send them my way.