4 ms·

I'm done with endless refactoring of .NET Core updates. The reality is they shipped RCs with 1.x version numbers. I will be back to reassess after Core 2.0 ge

by replete 10y ago

I'm done with endless refactoring of .NET Core updates. The reality is they shipped RCs with 1.x version numbers. I will be back to reassess after Core 2.0 gets a minor update. Microsoft suck at versioning. Progress is great, but we feel tricked.

pjmlp 10y ago
They were pretty clear from the early days that this was WIP, did you never watch a MS presentation?!
- baldfat 10y ago
  I agree that the talk has been from MS that this was a moving target and not ready for anything close to production till after 1.0.
AwesomeBean 10y ago
You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear. While I would love a simpler, more readable project file, I understand that the tooling already out there relying csproj format, probably makes it not worthwhile changing.
- rubber_duck 10y ago
  >You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear. Great and in those 10 months there was no alternative but to use the soon to be deprecated projects. And they released a 1.0 product like that. Someone from Microsoft commented unofficially that there was pressure from partners who were using .NET Core in production to release a stable - which was very obvious and they put them self in a spot where they had to support a deprecated project.json system since people are using it in production while also developing the new system. Whoever decided on the release timelines dropped the ball.
  - AwesomeBean 10y ago
    Well for the last 4 months, MSBuild alpha has been out with the option to use "dotnet migrate" to migrate a project.json to a project.csproj file. The other 6 months I agree has left people in a limbo. Only people following the discussions closely would have an idea of which direction they were going.

by replete 10y ago

pjmlp 10y ago

They were pretty clear from the early days that this was WIP, did you never watch a MS presentation?!

baldfat 10y ago
I agree that the talk has been from MS that this was a moving target and not ready for anything close to production till after 1.0.

AwesomeBean 10y ago

You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear. While I would love a simpler, more readable project file, I understand that the tooling already out there relying csproj format, probably makes it not worthwhile changing.

rubber_duck 10y ago
>You make it sound like this change was a snap decision. It's been known for at least 10 months now that project.json was going away. All the documentation I stumbled upon on github also made this clear. Great and in those 10 months there was no alternative but to use the soon to be deprecated projects. And they released a 1.0 product like that. Someone from Microsoft commented unofficially that there was pressure from partners who were using .NET Core in production to release a stable - which was very obvious and they put them self in a spot where they had to support a deprecated project.json system since people are using it in production while also developing the new system. Whoever decided on the release timelines dropped the ball.
- AwesomeBean 10y ago
  Well for the last 4 months, MSBuild alpha has been out with the option to use "dotnet migrate" to migrate a project.json to a project.csproj file. The other 6 months I agree has left people in a limbo. Only people following the discussions closely would have an idea of which direction they were going.