OK to address those: The micro packages are Microsoft packages which means they'll be testing them thoroughly and independencies between them will be recorded v

OK to address those: The micro packages are Microsoft packages which means they'll be testing them thoroughly and independencies between them will be recorded via NuGet. The whole "delete numbers and update" bit makes no sense given the NuGet update command. The point of current ASP.Net Core development is that they are being open about the sausage making process in order to avoid massive breaking changes in the future. Opening an MVC3 project has a defined update process because 3->6 has a massive update process. The team is aiming to only add new functionality going forward (at least for a very long time), they don't want to have to release Core 2.0 but 1.18. Things may break at the moment but that is almost certainly because you're hooked up to the MS CI build MyGet repository, certainly that is what the ASP Live streams are doing, so it is hardly surprising that things don't always work. They've just committed to 6+ weeks of fixing stuff before the RTM - stability will improve.