Skip to main content

Webinar - Hands on to "Sitecore 10 Content Serialization (SCS)"

 


 Hi Team,

At Horizontal Digital , we as a team decided to create set of webinars and online sessions for developers to help learn new concepts of "Sitecore 10" offerings.

As a part of that, different team mates started preparing for Sitecore 10 new features so those information can provided to the team and they can all push and learn SC10 in much better way and those topics can help them in their certifications too

 

As a part of those different webinars, I took the topic on "Sitecore Content Serialization (SCS)"

In SC10 certification one (out of many) competency is "Content serialization", We all have been working in TDS, Unicorn tools to serialize the content and use it to share, deploy sitecore content, but with SC10 there is a new way of serializing content.

Basically there are two ways which we can use SCS

1) Sitecore CLI : Is a dotnet core based command line interface, we can install nuget modules on top of this for SCS and we can start using Pull and push commands to serialize items back and  forth to/from Sitecore, No license is required

2) Sitecore for VS (SVS) : A developer can download Sitecore for VS Module VSIX package and install it in their VS studio, Existing TDS License will work otherwise one will need to purchase TDS license.

I will not write all the details of what are the perquisite to get started and what all GOTCHAs as i already have the below recording where i have shown complete DEMO and hands on of SCS

 Session can be found on following video

Hope you get your hands dirty with above demo and get started with SCS... 
Labels:

Comments

Post a Comment

Popular posts from this blog

High CPU to completely normal CPU - SXA issue, SXA pages not loading in mobile device

  Hi Team, Today i am going to share one of the nightmarish issue with you all, We are having Sitecore 9.1.1 hosted in azure PaaS environment Our site was working just fine and no noise, but we have been working on a feature release where 7-8 months of development needed to be released to production, Big GO LIVE event right?  Also to make the development smoother we also introduced BLUE/GREEN deployment slots in the same release, so we can easily SWAP slots and go live Everything went well, we went live, we even did load and performance testing on our staging and pre-prod and we were confident enough of results Very next day we started getting "SITE DOWN" alerts, and also product owners and clients mentioned that site is very slow for them in US time and in our morning when we were accessing it, it was working lighting fast so we were clue less at start, but we started digging  1) First thing caught our eyes were HIGH CPU spikes, in US time, also without any traffic CPU u...
3 comments
Read more

Sitecore Stream - Platform DxP Evolution

Hi Team, I am absolutely Sitecore Stream enthusiast, and if you also keep following what is new in it and explore it features, This blog post is for you Since it was announced in symposium 2024 and probably the first platform DxP version package was released in FEB-2025 and we are now in Sep end and there have been significant roll outs and we are into 6th release of the platform DxP package. The purpose of this blog post is to summarize all improvements which came along with different releases for all of you and community, If you have not explored all of the packages. NOTE : Remember Stream is "AI capabilities throughout the composable stack, be it Content Hub, XMC, CDP, Personalized but this blog post is only for platform DxP package for on-prem XP/XM. If you see the image above, i have tried to show the package rollout on the timeline as an when they were released and watchout for next package rollout, For other useful features :)  Important improvements 1) Less configurations ...
Post a Comment
Read more

An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.

You have noticed many times that everything was working fine and suddenly the below error starts coming and you find no way to work it out An error occurred while receiving the HTTP response to This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. The reason for this is the receiving size of WCF service is smaller then the data which is coming from service It was working before because it was small,So you will have to try to increase the receiving setting in your end point,Possible settings can be following maxStringContentLength="2147483647" maxReceivedMessageSize="2147483647" maxBufferSize="2147483647" maxArrayLength="2147483647" That would definately help you!!!
1 comment
Read more