Part of the upgrade in a Sitecore project is to remove the package.config file and change the way how we handle all Sitecore references. So, let’s follow these steps: Ok, so until here isn’t a big deal, right? So let’s do the following in the project At this point, you just need to add the

One of the critical things when we do an upgrade to our Sitecore Instance is to upgrade the code and the helix structure in the solution. So, I will describe the primary topics that everyone has to keep in mind in the upgrade process: Remove Gulp Files When we have an old solution using gulp

In this topic, I’m going to explain how to fix the installation process for the prerequisites and Sitecore. Prerequisites Since Microsoft deprecated the link for Web Platform Installer, we need to modify it with the new one, following these steps: it should look like this: Now, you can install all the prerequisites without issues. Sitecore

Sometimes we need to create a custom crawler in our solution in order to add custom items in our solr index that are not part of our Sitecore instance, for example, read an external API and add those results in the index. Ok, reading the API is the easy part of this, so let’s talk

In order to migrate to Sitecore.CLI 5.2.109 or greater over docker, we need to do the following steps: SITECORE CLI Open the backend folder project with a power shell terminal Run the following command: Then, after the upgrade is done run the following command for initializing the plugins Now, let’s verify the upgrade with the

Dianoga is a very helpful tool that allows us to compress images and use the new image formats in our Sitecore site. For installing it, we can do it manually or using a project in our Sitecore solution. In the solution, we need to add the nugget package called Dianoga For Sitecore using the nuget.org