Interesting bugs - MSB3246: Resolved file has a bad image, no metadata, or is otherwise inaccessible. Image is too small.
I got a very strange warning recently when building a .NET Core app with "dotnet build." MSB3246: Resolved file has a bad image, no metadata, or is otherwise inaccessible. Image is too small. Eek! It's clear, in that something is "too small" but what? A file I guess? Maybe it's the wrong size? The error code is MSB3246 which is nice and googleable/searchable but it was confusing because I couldn't figure our what file specifically. It just felt vague. BUT! I had recently been overclocking my machine (overly aggressively, gulp, about 40%) and had a very nasty hard reboot. As a result I had a few dozen files get orphaned - specifically the files were zero'ed out! Zero is small, right? Turns out you can pass parameters over to MSBuild from "dotnet build" and see what MSBuild is doing internally. For example, you could /fileLoggerParameters:verbosity=diagnostic but that's long. So how about: dotnet build /flp:v=diag Cool. Wha...