Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
MrCSharp595871dHow is that not helpful? If you have done logging properly and know how to place a few breakpoints in your code you'll actually be able to see what the Entity Framework validation error was.
But I'll make a guess to how you have done your logging: > log.Write(exception.Message);
MrCSharp595870d@Diactoros Exceptions in .Net are actually regular objects so they have properties. Printing out only the message property is not enough sometimes because the dev who created that exception object might not have put all the info in the message property. That's why it is recommended to use a structured logging library because you can pass the exception object and have all of its properties included with the log message.