{"id":39562,"date":"2020-06-10T06:00:18","date_gmt":"2020-06-10T13:00:18","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/premier-developer\/?p=39562"},"modified":"2020-06-02T08:40:18","modified_gmt":"2020-06-02T15:40:18","slug":"maintain-projects-with-different-sharepoint-framework-versions-using-azure-container-registry","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/maintain-projects-with-different-sharepoint-framework-versions-using-azure-container-registry\/","title":{"rendered":"Maintain projects with different SharePoint Framework versions using Azure Container Registry"},"content":{"rendered":"

In this post, App Dev Manager Norberto Planchart<\/a> demonstrates how to create and consume Docker containers for SPFx projects using Azure Container Registry.<\/p>\n

\n

SharePoint Framework (SPFx) is growing rapidly, which is good because in each version it gives us more and more features and functionality. But, on the other hand, it creates a problem for us when we must maintain our “old” projects that are already in production. Due to time constraints, we don’t always have the option to migrate to the latest version.<\/p>\n

If we must make a minor change, the ideal is to keep the project in its version, but surely our development environment is already in a higher version. In the past, the solution would be to have a virtual machine for each version that we maintain. But now we have containers, here is where Azure Container Register (ACR) will help us.<\/p>\n

ACR is a managed Docker registry service based on the open source Docker Registry 2.0. ACR is the ideal choice if we want to have standard images for all of our developers, shared images with our continuous integration (CI) processes, and manage everything from a single platform and provider.<\/p>\n

In this article we are going to see how to create and consume images to our SPFx projects.<\/p>\n

Prerequisites:<\/h3>\n

Azure:<\/h4>\n