Published on February 2, 2018 by Microsoft

In this second part of our discuss on the .NET Core 2.1 Roadmap, Scott Hunter, Richard Lander, Daniel Roth, and Andrew Peters return to go through demos of the new features.

  • [00:43] Global tools
  • [02:25] Windows Compatibility Pack for .NET Core
  • [05:12] SignalR on ASP .NET Core
  • [06:55] ASP .NET Core HTTPS and HSTS support
  • [08:00] ASP .NET Core GDPR support
  • [08:30] ASP .NET Core Identity UI
  • [09:12] Improvements for building Web APIs
  • [12:52] Managing HttpClient instances with HttpClientFactory
  • [16:05] Lazy Loading in Entity Framework Core 2.1
  • [18:52] CosmosDB support in Entity Framework Core 2.1
  • [21:36] Estimated Schedule

Feel free to reach out to our guests on Twitter to ask them any questions.

Leave a Reply

5 Comments on ".NET Core 2.1 Roadmap PT.2"

Notify of
avatar

Volodymyr
Guest
Volodymyr
6 days 19 minutes ago

Thanks a lot – we are waiting for at least RTM to try it 🙂

Neel
Guest
Neel
13 days 8 hours ago

Nice. I have written a post on Asp .Net Core 2.1 features which you can find here: neelbhatt.com/2018/02/06/asp-net-core-2-1-features/

Ponant
Guest
Ponant
13 days 8 hours ago
@divega , the UnitOfWork solution is super interesting! However, I totally agree with @TheSaintr and I can say upfront that, yes, you need to discuss more!I made a homemade -naive- EF provider for CosmosDb and the way to avoid collection creation per type was to do something like providing the collectionId in the optionsBuilder shown in OnConfiguring, instead of only the database name. The developer should be given the possibility on where to put his entity, i.e. the client name, the database and the collection. Only this will allow them to control pricing.An additional thing that could be done is… Read more »
divega
Guest
divega
16 days 5 hours ago
@TheSaintr:Thanks for the feedback! When we are done with the Cosmos DB support, we will have the ability to model documents as aggregates (a root entity type and a number of owned collections and references). Inheritance will use a collection per hierarchy.Then, based on the current plan, you will only have to create a collection for the root hierarchy, as all the owned entity types will be embedded as part of the document.We believe this is the most natural way to map EF Core models to a document database, but since as you said, in Cosmos DB, collections are the billing unit,… Read more »
TheSaintr
Guest
TheSaintr
16 days 7 hours ago

About EF Core CosmoDB.Isn’t creating a Documento Collection for each "entity" in EF the oposite of what nosql stands for.Also in terms of cost you pay for each collection thus imagine a 100 table SQL Azure…. converted to cosmoDb you pay a LOT for that!

wpDiscuz