Auto-detect potentially conflicting csproj files

Experience suggests that csproj files (either generated by some versions of Unity, or maybe visual studio) may switch dll locations.
After clarifying how the csproj files are generated, and why, may bother looking up dll locations from there, but until then a search pass flagging potentially conflicting csproj with an option to just delete them would be nice.