.NET Core 3.0 Concludes the .NET Framework API Porting Project

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by contravariant on Tuesday October 15, 2019 @07:16AM (#21257364)

I find structural typing is mostly necessary when someone messed up and used a class where an interface should have been used.

I'm now currently in the position of having to decide whether it's better to accept defeat or use T4 or similar to write the 1000+ line wrapper class to undo the mistake... You'd think Microsoft would at least remember to do dependency inversion through interfaces in their own C# code.

[ Parent | on HN ]

Re:.NET Core 3.0 Concludes the .NET Framework API Porting Pr... by LeonB on Tuesday October 15, 2019 @04:29PM (#21263372)

I wrote a tool, NimbleText which is free and good and lightweight for these one off 1000-line code generation scenarios. See https://nimbletext.com/live or email me for help (support at nimbletext)

[ Parent | on HN ]