Additional analyzers and refactorings for .NET serialization

[IanKemp]

There is a very thorough article by PVS-Studio that covers most of the common pitfalls around the odd beast that is .NET serialization. It would be useful if analyzers and refactorings could be added for these special cases, as debugging serialization issues can be a very frustrating and time-consuming process.

[josefpihrt]

It would be necessary to create an issue for each analyzer/refactoring and describe desired functionality including code sample.

[LesRamer]

Lacking a way to private-message you guys, I wanted to share something. I remembered reading a really interesting blog post on that viva64 site about the capability of their PVS-Studio code -- something called "the last line effect". Essentially as developers add new code, they tend to write new code by copying existing code and then neglecting to update some or all of the code that they've copied. I think you'll find at least the blunders in the code samples in these two entries extremely interesting even if you don't read the text of the entries. They have some entries where they copy an expression on the left of == to the right-side without modifying -- resulting in an expression that should always evaluate to the same value, so it's not always a full line of code that is copied (although it might regularly be on the last line.) Cheers!

https://www.viva64.com/en/b/0485/ <-- The Last Line Effect Explained
https://www.viva64.com/en/b/0260/ <-- The Last Line Effect