Avast marks the EXE built by Visual Studio 2010 for a simple VB.Net solution I created this morning as a virus, preventing it from running, even when launched by Visual Studio for debug. (Win32:Evo-gen[Susp])
I could maybe add Visual Studio's "Projects" directory to the AV exclusion list, but I find I am having to do this more and more and more recently for any code that I need to compile, be it Visual Studio, Eclipse CDT, or even just DevShed-C++.
It will very soon get to the point where I will be worrying that excluding so many directories and their sub-directories may leave me open to the situation where a virus *does* locate itself into one of these directories!
I note a rash of similar posts on these forums from sometime last year, I wasn't building VB stuff then but haven't had issues in the last few months until just recently, so I guess something in the virus definitions may have been added back where it shouldn't have been?
Is there anything I can do to prevent my VB programs from causing these false positives?