.Net core 3.0 breaking changes
-
I guess you may already know this but still, it's pretty annoying for me. Dudes just introduced breaking change in the order of startup methods in a framework used by really lots of people because of... um... oh... whatever reason.
-
I guess you may already know this but still, it's pretty annoying for me. Dudes just introduced breaking change in the order of startup methods in a framework used by really lots of people because of... um... oh... whatever reason.
I had to create a template ASP.NET Core 3 project just to figure out why things were breaking in the whole startup process. Geez, they changed a lot. And then I also discovered that they switch to their own JSON deserializer -- apparently they had been using Newtson, and that broke things. Then I discovered that the way I was coding a SQL where clause with EF "linq-ish" syntax no longer was supported. I hate open source.
Latest Articles:
Abusing Extension Methods, Null Continuation, and Null Coalescence Operators -
I had to create a template ASP.NET Core 3 project just to figure out why things were breaking in the whole startup process. Geez, they changed a lot. And then I also discovered that they switch to their own JSON deserializer -- apparently they had been using Newtson, and that broke things. Then I discovered that the way I was coding a SQL where clause with EF "linq-ish" syntax no longer was supported. I hate open source.
Latest Articles:
Abusing Extension Methods, Null Continuation, and Null Coalescence OperatorsQuote:
And then I also discovered that they switch to their own JSON deserializer
This thing "wow, this new JSON serializer is so fast" really annoys me. Of course, it's fast, it lacks features Newtonsoft has. There are lots of other fast serializers with a lack of features i.e. Utf8Json, why not compare with them. It's worth noting that one can use Messagepack to serialize things fast.
Quote:
I hate open source.
I wonder whether this is open source or just sloppiness.