|
|
|
|
|
by FubarCoder
3692 days ago
|
|
The main feature - for me - was the ability to use the same project.json to compile a project for multiple frameworks. Sad to see, that they ditch project.json - especially after the overhaul one or two weeks ago, which was a necessary cleanup. How will they be able to release the rc2 on May, 16th, week they change a critical part of the build chain again? Does this mean, that they are ditching dotnet CLI too? |
|
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"