Session Machine Learning et .NET avec ML.NET au Diginova 2019

Pour cette session en compagnie de Christopher Maneu (Microsoft France R&D), j’ai eu le plaisir de pouvoir parler de ML.NET, cette bibliothèque que l’on a déjà implémenté dans un produit et qui fonctionne à merveille (ou presque quand ce ticket aura été corrigé) et qui permet à tout développeur d’intégrer du Machine Learning dans ses applications .NET.

Ce duo avec Christophe a permis de comparer les solutions et de préciser les différents scénarios d’utilisation des services et framewok que Microsoft met à disposition des développeurs (ACS, CNTK, ML.NET) : quand l’utiliser, les scénarios connectés/déconnectés d’ACS et ML.NET, quel effort de montée en compétence pour les développeurs (SDK + apprentissage du Machine Learning), etc.

Un sujet extrêmement intéressant qu’il a fallut traiter en peu de temps .. .mais qui sera traiter plus en profondeur au prochaine Afterworks Microsoft 😉

IMPORTANT NOTE : .NET Core Container Images now Published to Microsoft Container Registry

THIS IS AN IMPORTANT ANNOUNCEMENT: Microsoft is now publishing .NET Core container images to Microsoft Container Registry (MCR).

Note that Microsoft will continue to maintain Docker Hub repo pages so that you can discover and learn about .NET Core images. The Docker Hub website URLs you’ve used for Microsoft repos will continue to work, and forward to updated locations on Docker Hub.

Important :

  • Microsoft also made other changes to the images we publish, described in this post.
  • You will need to change FROM statements in Dockerfile files and docker pull commands as a result of these changes. 3.0 references need to be changed now. Most 1.x and 2.x usages can be changed over time. The new tag scheme is decribed in this post and are provided at the microsoft-dotnet-core repo, Microsoft new home on Docker Hub.

For more informations, please refer to this post on .NET Blog.

Reminder : .NET Core 1.0 and 1.1 will reach END OF LIFE on June 27, 2019

.NET Core 1.0 was released on June 27 2016 and .NET Core 1.1 was released on November 16 2016. As an LTS release, .NET Core 1.0 is supported for 3 years and .NET Core 1.1 fits into the same support timeframe as .NET Core 1.0.

So in short : .NET Core 1.0 and 1.1 will reach end of life and go out of support on June 27, 2019.

After this date of June 27, 2019, .NET Core updates will no longer include updated packages or Docker container images for .NET Core 1.0 and 1.1. But wait, no panic and this is for the best, upgrade from .NET Core 1.x to .NET Core 2.1 or 2.2.

.NET Core 2.1 is a long-term support (LTS) release so makes it your minimum standard for your development, even if I encourage you to use .NET Core 2.2. Why .NET Core 2.1 at least and not .NET Core 2.0 ? Because .NET Core 2.0 has already reached end-of-life, as of October 1, 2018

Upgrade to .NET Core 2.x

The supported upgrade path for .NET Core 1.x applications is via .NET Core 2.1 or 2.2. Instructions for upgrading can be found in the following documents (equally apply to .NET Core 2.1) :

The migration is quick and easy but be sure to bulletproof your application with heavy testing, I already found several minor issues while migrating from 1.1 to 2.1.