I can't say this is ideal. I've hacked my fair share of MSBuild files since .Net 1.0 and the experience is totally abysmal. That being said, its still somewhat readable, even though the schema reminds me of the overly verbose days of Soap XML 😄 I would've liked to see some more love brought into the project.json, but if there isn't a unified effort behind the project, they're right in getting rid of it.
Perhaps a better solution is to abstract a lot of the pain into a smaller DSL, wherein we use recipes to configure, but time will tell on that one. In the end most .Net engineers use Visual Studio which is magnificent at hacking those monsters so the problem is minimal... until you mess something up.
follow-up: http://xoofx.com/blog/2016/05/11/goodbye-project-json/
I can't say this is ideal. I've hacked my fair share of MSBuild files since .Net 1.0 and the experience is totally abysmal. That being said, its still somewhat readable, even though the schema reminds me of the overly verbose days of Soap XML 😄 I would've liked to see some more love brought into the project.json, but if there isn't a unified effort behind the project, they're right in getting rid of it.
Perhaps a better solution is to abstract a lot of the pain into a smaller DSL, wherein we use recipes to configure, but time will tell on that one. In the end most .Net engineers use Visual Studio which is magnificent at hacking those monsters so the problem is minimal... until you mess something up.