Since switching to a new computer with VS2015 (from VS2013), Unity3d sometimes suddenly throws harmless warnings (cs0219 & cs0414, i.e. an assigned variable or field that is never used) as errors that block me from compiling. Besides actually “fixing” these warnings there’s this dissatisfactory workaround: close unity3d and vs2015 and reopen them again. Then it won’t complain about those warnings for a while until it suddenly considers them errors again.
I’ve read about someone running into this issues because of a virus scanner, is that possible (am using a different one than on old computer (McAffee instead of Avira)?
The VS project’s settings have “treat warnings as errors” set to None, so I don’t understand why this happens. The seemingly random frequency of when this happens looks suspiciously like an “outside” cause. Any ideas?
running windows 10 and unity 5.0.3
Just to update this:
getting rid of that particular virus scanner seems to have solved the problem for me, so if you run into a similar issue, consider it as an option to try.
