Gotcha with .globalconfig and Visual Studio
VS will always apply a `.globalconfig`, not just when analyzers are activated like the CLI build does. Use a different name and explicit inclusion to get consistent behavior.
Just for fun: changing runtime behavior with unreachable code
Unreachable code can still change compiler behavior and thus runtime method behavior. An example with `yield`.
Nuget Packaging Series 2: Beware of DLL version conflicts
Putting assemblies with different TFMs in the same nuget package can lead to runtime assembly loading errors because of transitive assembly reference version conflicts.
Closed Type Hierarchies with records … NOT!
TL;DR: You cannot create closed type hierarchies with record types because of the generated protected copy constructor.
Record type gotcha with FluentAssertions 5
Use version 6+ of FluentAssertions when asserting equality of record types with collections in them.
Gotcha with C# 9 Record inheritance and ToString()
On record types, ToString() and other compiler-synthesized methods cannot be overridden up the inheritance hierarchy in parent records, but must be overridden in the concrete record.
Gotcha with xsd.exe and XmlSerializer
TL;DR: Always use the /order option when using xsd.exe. If you have ever generated C# classes from an XML schema, chances are you used xsd.exe for that.You probably also expected…
Gotcha during migration to async/await
TL;DR: Use Lindhart.Analyser.MissingAwaitWarning to get warnings on all ignored Tasks We all know and love compiler warning CS4014 for ignoring Tasks.You would think that this warning triggers every time we…