4 ms·
What's not a myth is that they got rid of their JSON configuration in .NET Core in order to keep their XML abomination. I really wish they'd revisit that and at
by hajile 5y ago
What's not a myth is that they got rid of their JSON configuration in .NET Core in order to keep their XML abomination. I really wish they'd revisit that and at least allow both options.
- e-master 5y agoAt first I thought that to be a mistake also, but I gotta admit I don’t mind at all using xml in the new sdk-style csproj files now, it certainly made upgrading legacy project files slightly simpler.
- aliswe 5y agothe "abomination" is like 1% of its former size, i dont really understand what merits this name...
- manigandham 5y agoModern .NET csproj/sln files are a few lines at most. As config files grow, XML is far better than JSON because it's much more structured (even if it has more verbosity). Do you have a problem editing HTML? Because that's quite literally XML.