>My problem with C# server development until recently has been the reliance on visual studio. TBH there are very few IDEs or environments that match Visual Stu

>My problem with C# server development until recently has been the reliance on visual studio. TBH there are very few IDEs or environments that match Visual Studio. If you've never used it, of course you'll be less productive. >A lot of configurations need to be done through VS and lead to the creation of config files that cannot be edited or read outside of VS. Project and solution files have been XML for a long while. I think the example here would be early UI work with WinForms and WPF? But everyone would think you're crazy to edit those text-only when you had a WYSIWYG editor. >And a lot of the “magic” in the .Net server technologies mean that when things go wrong, there’s almost nothing you can do other than raise a ticket with MS >Fortunately, both of these issues have been resolved with the open source .Net Core If there's an issue with Kestrel, I think you'll still be spending a long amount of time debugging that. I don't think much has changed on that front. .NET Core isn't a magic solution to this.