Update CICD scripts to new Sitecore NuGet URLs to avoid interruptions

If you are not already aware, Sitecore is moving its public feed from sitecore.myget.org to a different feed provider on November 30, 2023.

The URL of the new public feed is: https://nuget.sitecore.com/resources/v3/index.json
The URL for the internal artifact provider is: https://cloudsmith.io/~sitecore/repos/resources/groups/
The custom NPM feed will move from https://sitecore.myget.org/gallery/sc-npm-packages to the public NPM provider https://www.npmjs.com/

Both the original MyGet and the new public feeds are available now. After November 30, only the new NuGet and NPMJS public feeds will be available.

Sitecore strongly recommends that all customers and partners update their CI/CD processes and build scripts to use the new public feeds as soon as possible to avoid interruptions beyond November 30, 2023.

The above information is shared by Sitecore here.

How this can impact you?

This can impact you if you are making use of these URLs. Such URLS are usually used in Build/Release (CI/CD) pipelines. For example, I observed the below exception in my release pipeline during a recent release that I triggered to higher environment.

If you look carefully in snapshot, you will see the below line - NuGet.Protocol.Core.Types.FatalProtocolException: Unable to load the service index for source https://sitecore.myget.org/F/sc-packages/api/v3/index.json.

If you will try to browse this URL, you will see it is not responsive -

Sitecore claims that this URL shall be active till November 2023. This means it is temporarily down and should be back soon. But if you don't plan for this change of these URLs soon in your scripts/solution, you may face a similar error soon.

Hope it helps you! Thanks for reading!

Sitecore PowerShell Script to create all language versions for an item from en version

We have lots of media items and our business wants to copy the data from en version of media item to all other language versions defined in System/Languages. This ensures that media is available in all the languages. So, we created the below powershell script to achieve the same - #Get all language versions defined in System/Languages $languages = Get-ChildItem /sitecore/System/Languages -recurse | Select $_.name | Where-Object {$_.name -ne "en"} | Select Name #Ensuring correct items are updated by comparing the template ID $items = Get-ChildItem -Path "/sitecore/media library/MyProjects" -Recurse | Where-Object {'<media item template id>' -contains $_.TemplateID} #Bulk update context to improve performance New-UsingBlock (New-Object Sitecore.Data.BulkUpdateContext) { foreach($item in $items){ foreach($language in $languages){ $languageVersion = Get-Item -Path $item.Paths.Path -Language $language.Name #Check if language versi

Export Sitecore media library files to zip using SPE

If you ever require to export Sitecore media files to zip (may be to optimize them), SPE (Sitecore Powershell Extension) has probably the easiest way to do this for you. It's as easy as the below 3 steps - 1. Right click on your folder (icons folder in snap)>Click on Scripts> Click on Download 2. SPE will start zipping all the media files placed within this folder. 3. Once zipping is done, you will see the Download option in the next screen. Click Download Zip containing the media files within is available on your local machine. You can play around with the images now. Hope this helps!! Like and Share ;)

Make Sitecore instance faster using Roslyn Compiler

When we install the Sitecore instance on local, the first load is slow. After each code deploy also, it takes a while for the Sitecore instance to load and experience editor to come up. For us, the load time for Sitecore instance on local machines was around 4 minutes. We started looking for ways to minimize it and found that if we update our Web.config to use Roslyn compiler and include the relevant Nugets into the project, our load times will improve. We followed the simple steps - Go to the Project you wish to add the NuGet package and right click the project and click 'Manage NuGet Packages'. Make sure your 'Package Source' is set to nuget.org and go to the 'Browse' Tab and search Microsoft.CodeDom.Providers.DotNetCompilerPlatform. Install whichever version you desire, make sure you note which version you installed. You can learn more about it here . After installation, deploy your project, make sure the Microsoft.CodeDom.Providers.DotNetCompilerPlatform.d

Experience of a first time Sitecore MVP

The Journey I have been working in Sitecore for almost 10 years now. When I was a beginner in Sitecore, I was highly impressed by the incredible community support. In fact, my initial Sitecore learning path was entirely based on community written blogs on Sitecore. During a discussion with my then technology lead Neeraj Gulia , he proposed the idea that I should start giving back to developer community whenever I get chance. Just like I have been helped by many developers via online blogs, stackoverflow etc., I should also try to help others. Fast forward a few years and I met Nehemiah Jeyakumar (now an MVP). He had a big archive of his technical notes in the form Sitecore blogs. I realized my first blog dont have to be perfect and it can be as simple as notes to a specific problem for reference in future. That's when I probably created my first blog post on Sitecore. At that time, I didn't knew about the Sitecore MVP program. Over the years, I gained more confidence to write

Clean Coding Principles in CSharp

A code shall be easy to read and understand. In this post, I am outlining basic principles about clean coding after researching through expert recommended books, trainings and based on my experience. A common example to start with is a variable declaration like - int i The above statement did not clarify the purpose of variable i. However, the same variable can be declared as - int pageNumber The moment we declared the variable as int pageNumber, our brain realized that the variable is going to store the value for number of pages. We have set the context in our brain now and it is ready to understand what the code is going to do next with these page numbers. This is one of the basic advantages of clean coding. Reasons for clean coding - • Reading clean code is easier - Every code is revisited after certain amount of time either by the same or different developer who created it. In both the cases, if the code is unclean, its difficult to understand and update it. • To avoid s

Ghanendra's Tips

Search This Blog