[mking1024]

Really? We haven't had any problems with our .NET Core projects (a few web apps running on core and a bunch of libraries targeting core). In addition, ASP.NET Core (on .NET core) has been a great stack so far (using it since beta5); I feel very productive with it as well as enjoying the development experience. Why do people need to get fired for this? It doesn't seem like it will be hard to move from project.json back to (a new and improved) csproj.

[DSteinmann]

Yes, Really, and I am sure there are some people who have had no problems. That doesn't invalidate the countless hours I spent making this dreadful system work. Did you put it on your build server without installing Visual Studio on it?

[dsp1234]

Our build server (TeamCity) does not have VS installed.

I can actually tell you the exact software installed on the build server:

  1.) Window Server 2016 (Base OS)
  2.) SQL Server 2016 Express with LocalDB only (used for longer integration tests that need to validate migrations)
  3.) DotNetCore.1.0.1-SDK.1.0.0.Preview2-003133-x64.exe (.NET core SDK 1.0.1 download from https://www.microsoft.com/net/download)
  4.) BuildTools_Full.exe ("Microsoft Build Tools 2015 Update 3" https://www.visualstudio.com/downloads/#d-build-tools).  If you have this, then you don't need the full VS install
  5.) NodeJs (for running webpack as part of 'dotnet publish')
  6.) TeamCity and Octopus Deploy agents

That's it.

[colemickens]

>Did you put it on your build server without installing Visual Studio on it?

Huh?

`docker run microsoft/dotnet`. Took about 2 seconds to get it running on my Jenkins build server. In reality, it took literally no effort. My entire full stack app requires `make` and `docker` to build and nothing else. The backend is an AspNetCore API.

[mattmanser]

Everyone's been having problems with them, how can you have had none?

They seem to massively change something every 10 minutes.

I also don't get the 'massively productive' comment, in essence very little has changed since, hell even MVC 3, apart from the obsession with DI and a load of packages now don't work. If you weren't 'massively productive' before, you were probably doing something wrong. They just moved a couple of things around and now insist you use npm/bower/whatever hotness they latch onto next week instead of nuget. I'm sure we'll have another blog post about them ditching support for anything but yarn next week.

And how long before they change their minds about how controllers work again, it's been like 4 times in the last 5 years now. First MVC controllers, then Web API, then Web API 2, then OData, then .Net Core, all very similar but slightly different with slightly different ways to register them at startup and slightly different things available on the context. Apart from the utter madness that is OData, great for data tables, bloody awful for everything else.

It's getting almost as bad as javascript churn but it's one company so it doesn't make any sense.

[cmdkeen]

It changed during the pre-1.0 era when the team were very clear about the potential for changes. The big changes were made with plenty of notice and short term backwards compatibility baked in. MVC 5 is still there and still being supported - deliberately choosing to use Core should have been a calculated decision based on what you needed and appetite for risk. If there's a bad influence from the world of JS it seems much more around devs deciding to go into production with "the new hotness".

Moving to npm/bower for front end stuff makes perfect sense, NuGet is a horrible way to deliver client side code, wasn't supported by the majority of library producers and was unknown by anyone who didn't have a .Net background.

[jsingleton]

I expected changes at the beta stage. I did not expect the major changes between RC1 and RC2. Try writing a book against a moving target! :)

I think all the changes now are due to that late switch of direction. RC2 went straight to 1.0 but it was a major change and should probably have had some more beta/RC releases.

[UK-AL]

It's was an alpha/beta/prerelease product, you should expect change.

[DSteinmann]

It's not just change. It's difficult to make it work for a single version. It was difficult back when the build tools were a handful of powershell scripts. It was difficult when they moved to the dotnet tooling.

Microsoft shouldn't push out an RTM product and call the broken bits "Preview" to absolve themselves of the responsibility to deliver a reliable product.

I was evangelical about .NET Core. I stuck with it for years. I stuck with it when Damian admitted that he "doesn't build web apps". I stuck with it during the Release Candidates. It's only when they pushed this out the door and called it RTM that the penny dropped and I accepted the project had been mismanaged.

[nightski]

They announced all of this before .NET Core went RTM. Not only that, the tooling was never made RTM (still in preview). If you jumped on the bandwagon that early then you had all of this information and knew what was coming.

[manigandham]

You should just wait until both the framework and tooling are RTM if that's the stability you need - the framework is already great but if you need the tooling then wait until it's ready.

Why complain if you understood the status and assumed the risk?

[mattmanser]

Microsoft have always had extremely stable RCs.

If you knew anything of the traditional release history for Microsoft you wouldn't have commented. All your post demonstrates is total ignorance of the context or history.

It was previously totally fine to use RCs for the last decade, probably way before that too, but I only have experience from then. RC in MS speak meant "pretty much finished, API won't change unless we find something desperately wrong".

Then it suddenly means basically pre-alpha, "anything can change, massively, between RC versions".

[manigandham]

Great, it's still RC vs RTM. Past history doesn't mean forever. This is still your interpretation of what an RC means getting you into trouble.

[manigandham]

> They seem to massively change something every 10 minutes.

> in essence very little has changed since

?

The one thing Microsoft is great at is compatibility. Your existing projects can keep using the older frameworks and they're still supported and will run just fine. What is the issue? If it's about learning the new changes, then it's probably best to wait until everything (framework + tooling) are final so you only have to learn once.

[mattmanser]

I honestly have no idea what point you're trying to make.

The problem is that it's hard to understand what does what and how it does it. Things in even the same project behave differently. They introduce massive architectural changes and then abandon them. Searching for something in SO now is a crap shoot, which slightly in correct answer will you get because the asp.net team changed their mind again?

And you can have all these things running in one project, all acting differently.

I work with clients on MVC 3,4,5, with parts in web API 1 and 2 and parts in odata.

And they all behave differently.

For example, and this is just one of many, a JSON date from an MVC controller is 'Date(173737273)', from a web API it's '2016-12-26 23:00:00.0000', from an OData controller it's '2016-12-26 23:00:00.0000Z'. That Z changes behaviour btw and makes the terrible assumption your date is in the same TZ as your server.

All of them are parsed different and will return different dates in javascript.

[douche]

This is why I'm glad that we are using Nancy. It has been far more stable.