I have a simple little Unity Assets Monitor that takes a Unity project path, and outputs a csv file and a text file. It is released, and I have had no problems until today.
Today I updated my lists with a few additional file extensions, then tried to run a debug test from within Visual Studio 2015 Community. The program built, but when it tried to launch Avast threw up a Win32.Evo-gen(Susp) pop-up message, and promptly removed the file.
I tested creating a release build and debugging that directly within VS, and there is no problem, it only happens when running in debug and clicking start within VS. Please could you investigate. I have submitted the file as a false positive for you.
It’s not the application that is the problem, I can launch the built debug application fine, for some reason it is when VS starts debugging this application from within VS in degub mode the problem occurs. If I do exactly the same in release mode, there is no problem.
I submitted this via the system tray app as a false positive when it occurred. I can submit the file again, but this issue only occurs when the debug build has the debugger attached. The debug build runs fine on it’s own. I think this is more to do with the interaction of the debugger and the app.