I recently built a web app with the new dotnet core . the changes were not so bad, I even found that the docs were nicer than the ones you find for the "old" asp.
After having to configure camalCase for json a couple of times I like the new default.
But migrating an existing app at this point is out of the question, when I no longer need to have nugget packages with rc in the version name we might do it.
No I'm talking about the version numbers themselves, things like:
1.0.0-preview2-final
I will not take a working(and money-making) code base and migrate it to a platform where that is the version I need to use.
As for project.json. I actually liked using JSON over XML, but it's a personal preference thing, can't really make a case that it's better.
Comments
I recently built a web app with the new dotnet core . the changes were not so bad, I even found that the docs were nicer than the ones you find for the "old" asp.
After having to configure camalCase for json a couple of times I like the new default.
But migrating an existing app at this point is out of the question, when I no longer need to have nugget packages with rc in the version name we might do it.
If you're talking about project.json, it's already dead :/ http://xoofx.com/blog/2016/05/11/goodbye-project-json/
No I'm talking about the version numbers themselves, things like: 1.0.0-preview2-final I will not take a working(and money-making) code base and migrate it to a platform where that is the version I need to use.
As for project.json. I actually liked using JSON over XML, but it's a personal preference thing, can't really make a case that it's better.