recursive exclusion

[spetroff]

Is it possible to tell Avast! to exclude all files of a particular extension in a specified directory and all subdirectories? I'm a software developer and it seems that when I do a full compile, Avast! is scanning the compiler's output. Given that a full compile produces several thousand files, I'd like to stop the scan. There is no way to hard wire all possible exclusions with the UI tools (I have excluded the compiler itself along with various related services). I'm hoping that there is something like a recursive option I can specify in the exclusion text to tell Avast! to ignore all class files produced under a specific build directory. Either that or a command line option which I can execute as part of the build script to shut down the standard shield before a compile, then start it back up afterwards.

--
Shane

[igor]

Well, how about using wildcards?

[spetroff]

Well, how about using wildcards?

BTDT, if wildcards had worked in the first place, I wouldn't have posted the question.

[RejZoR]

And how you used wildcards?

[igor]

The wildcards work. I suggest to post the exact folder/files that you want to exclude, and also the masks you tried.

[Lisandro]

Just remember that wildcards use text string. So:

C:\Program files\*.*

is different of

C:\PROGRA~1\