3 ms·
Out of interest, what "patterns from the .NET framework era" do you think don't work well in .Net core? ( I'm someone who deals all day with legacy .Net framew
by eterm 2y ago
Out of interest, what "patterns from the .NET framework era" do you think don't work well in .Net core?
( I'm someone who deals all day with legacy .Net framework projects, mixed with the kind of mix of .Net core 3, .Net 6, .net standard 2.0, and .Net 8 projects that you'd expect from a 20+ year old company with 260+ projects. And yes, I too envy hobbyists at time. )
- hnthrow289570 2y ago>Out of interest, what "patterns from the .NET framework era" do you think don't work well in .Net core? Overriding equals to do memberwise comparisons on POCOs Any checking of types where pattern matching would be better Old-style tuples without names (old style is tuple.Item1, tuple.Item2, etc.) Checking of multiple tuple values at once without pattern matching Any code that could be refactored with the new LINQ methods Long ifs/switches that could be replaced by pattern matching Concatenate a lot of strings (one per line) so there wasn't a ton of horizontal scroll, particularly for SQL in C# code using statements still needing a level of nesting