.NET random assembly being modified on disk

One of our applications starts suddenly with the error "Unable to load file or assembly". After some research, I found that one of the DLLs used by the application changed its size by 1-2 bytes.

After playing with it, I realized that it was related to all the DLLs used by the application and any of them could get corrupted. We have the same copy of the app on a different box and it works without issue. This makes me think it has to do with the environment.

How do you know which process is modifying the file and when? What could be the reason? Has this happened to any1?


source to share

1 answer

If you have access to the computer where this is happening, you can use FileMon to monitor your build files and figure out which process is modifying them.

It sounds suspicious like some kind of virus or antivirus has disappeared.



All Articles