In January 2017 I decided it was time to "upgrade" YetaWF from MVC 5 to the new ASP.NET Core MVC. Oh, and how much fun it was (Not!). I spent about 2 months converting silly (and major) things which changed between MVC 5 and ASP.NET Core (see Incompatibilities Galore). So, after two months I had a working, deployable version of YetaWF. Was it any better than the version running with MVC 5? No. Looks and feels exactly the same. Is it faster? No. It's the same damn thing...
The worst part here was that ASP.NET Core 1.1 had several flaws so I had to switch to the dev version of ASP.NET Core MVC (1.2 renamed) 2.0. So I was comitted to using 2.0.
Then, a few days ago, ASP.NET Core MVC decided to switch to netcoreapp2.0. This means it's no longer based on .NET 4.6. WTF! The entire solution and all its 50+ project (for the basic YetaWF install) have to be converted to netcoreapp2.0. YES! Let's do it! It'll be awesome... So once I'm done what do I have? The exact same thing. Looks and feels exactly the same. Is it faster? No. It's the same damn thing...
Seriously! I'm not willing to do this everytime someone has a brainfart at Microsoft... And the production sites which we run based on YetaWF won't be able to "upgrade" to ASP.NET Core MVC 2.0 anyway because they use some 3rd party assemblies, some silly old, that simply won't work. Fortunately, YetaWF also supports ASP.NET 4 with MVC 5. Did I mention, it looks and feels exactly the same?
So, for God's sake, why do you (Microsoft) keep changing things SO DRASTICALLY, days before the anticipated preview version??? This post says it best: https://what.thedailywtf.com/topic/22876/microsoft-*****-their-developers-in-the-***-again