Re:Project.json is dead. ASP.NET Core goes back to MSBuild
by alexc05 on Thursday May 12, 2016 @07:25AM
(#11682629)
No, dotnet CLI is coming along for sure.
I was watching the community stand-up on Tuesday where Scott Hanselman and Damien Edwards discussed the reasoning in a little more detail.
They were pretty clear that they wanted to make sure they adapted and kept all the things they liked about project.json
And then rattled off a list.
I'm sure the single-file for multiple frameworks would be on the list of things they want to keep.
The shift to CSPROJ for them actually sounded (relatively) simple.
The current project.json becomes a PropertyGroup and they put everything inside that.
So they switch the mustaches for triangle brackets, but they did mention wanting to keep it "light weight"
I also know that Damien said something to the effect of "we loved project.json probably MORE than many members of the community, but the choice had to be made"
I was watching the community stand-up on Tuesday where Scott Hanselman and Damien Edwards discussed the reasoning in a little more detail.
They were pretty clear that they wanted to make sure they adapted and kept all the things they liked about project.json
And then rattled off a list.
I'm sure the single-file for multiple frameworks would be on the list of things they want to keep.
The shift to CSPROJ for them actually sounded (relatively) simple.
The current project.json becomes a PropertyGroup and they put everything inside that.
So they switch the mustaches for triangle brackets, but they did mention wanting to keep it "light weight"
I also know that Damien said something to the effect of "we loved project.json probably MORE than many members of the community, but the choice had to be made"