DEV Community

Discussion on: Developer eXperience: error messages

Collapse
 
codevault profile image
Sergiu Mureşan • Edited

I can safely attest the fact that log message blindness is a thing. A couple weeks ago I had some dependency issues in .NET and couldn't figure out any solution after trying for a couple hours until... you guessed it... I looked at the log:

C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1697,5): warning MSB3247: 
Found conflicts between different versions of the same dependent assembly. 
In Visual Studio, double-click this warning (or select it and press Enter) to fix the conflicts; 
otherwise, add the following binding redirects to the "runtime" 
node in the application configuration file: 


<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly><assemblyIdentity name="Newtonsoft.Json" culture="neutral"
 publicKeyToken="30ad4fe6b2a6aeed" /><bindingRedirect oldVersion="0.0.0.0-11.0.0.0" newVersion="11.0.0.0" /></dependentAssembly></assemblyBinding>

Right there, the problem AND the solution. I was face-palming so hard after I saw that. Sadly, both our build log and our front-end console log is flooded with useless information, part our fault, part Visual Studio's.

The main takeaway from this... read the build log if you have build errors.