, Tennis Player, Father and Husband
@davidfowl it's an uphill battle to change some things and we changed everything all at once.
I was in the meeting where we decided to retired project.json. The problem is that the .NET ecosystem is large and growing
-
-
-
@davidfowl the tension is that web the web landscape very different from the rest of .NET -
@davidfowl so if we diverge, it ends up breaking muscle memory. -
@davidfowl didn't we break muscle memory like at least a year ago? -
@aggieben not the masses. Just the bleeding edgers
End of conversation
New conversation -
-
-
@davidfowl Hopefully it'll mean we can support existing .NET 4.5 projects along side .NET Core with the same .csproj? Was a broken UX before -
@demisbellot what does alongside mean to you? In the same solution? -
@davidfowl Yeah with#defs - just having a project.json before would break existing .csproj - main reason I put it off until it was resolved -
@demisbellot yes that's a big
- End of conversation
New conversation -
-
-
@davidfowl does this mean nuget 3 is also going to stop using it and go back to sln-level storage & packages.config? - End of conversation
New conversation -
-
-
@davidfowl Is this RC2 related or later? -
@davidfowl Guys, I trust you but later than RC2 means almost RTM and that's looks like a breaking change.. Still, I trust your choice.
End of conversation
New conversation -
-
-
@davidfowl Do you understand the pain of editing xml files by hand for those who use a cli ? -
@davidfowl Hey sorry my previous message wasn't directly addressed to you, I know you know. Thanks for your work.
End of conversation
New conversation -
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@davidfowl
unfortunately it's not the 1st of April.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.