#realJSOP wrote:
So how is the crappy data format affecting the usability of .net framework vs .net core?
It isn't. I just had some issues going back to .NET Framework, but, unrelated, that wasn't my biggest problem because that is the data format.
#realJSOP wrote:
How is .net core a panacea?
I wouldn't call it a panacea, it has its issues (like no WCF/SOAP support). But it comes with DI out of the box, it's right there and all your need to do is add a few lines of services.AddTransient<ISomeService, SomeService>(); The same goes for logging, just add some loggers through extensions and inject ILogger. Or EF Core for that matter (turned out I can just use EF Core in .NET Framework too). And the configuration is read from a JSON file, and nowhere has it been as big as my smallest .NET Framework XML config file. It's also super easy to map JSON objects to .NET classes, so instead of putting everything in <appSettings> just add "SomeSetting": { "SomeSubSetting": { "SomeSubSubSetting": [ "v1", "v2" ] } } and it works. And with the ConfigurationBuilder I can just add builder.AddAzureKeyVault("[uri]"); and it'll add all my KV secrets like they were in my config file to begin with. Maybe it's not so much .NET Framework, but WCF, which is rather archaic in 2019 (no easy support for DI, so I had to use Unity or Windsor or MapSomething, went with a Unity plugin). I have it all set up now, but it cost me a while to figure it out.
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly