TDS: The Evolution of Auto-Sync

March 16, 2016 | Sean Holmesby

Team Development for Sitecore (TDS) is currently in beta, and is due to be officially released to the public next week. I've been lucky to have already played with the impressive list of new additions in v5.5, and loved the further improvements to my Sitecore development efficiency. Features like the new Delta Deploy feature, and the Auto Deployment of Content Files have me doing Sitecore development quicker than ever. One big new addition available in TDS v5.5 is the AutoSync feature... Another efficiency helper, where Sitecore changes get synced back to the TDS project automatically. It has been described as a 'new' feature.... But is it? Really, Auto-Sync has existed in TDS for a while, it's just taken on a new form in v5.5. Let me explain what I mean by this. Back in 2010 TDS v3.0 introduced the TDS <=> Sitecore Rocks connector. This connector meant that changes made using Sitecore Rocks were automatically synced into the TDS project. A developer would add templates, layouts, and edit content in Rocks.... and without doing any extra work, these changes were pulled in to the TDS project. Sure, it's not what we mean by AutoSync in TDS v5.5.... but that's exactly what it's doing... it's auto-syncing a developers changes into the project. 2010 huh? It's 'new' on a geological timescale.... but not on a development timescale. :-P But the feature updates didn't end there... In 2013 and 2014, Sitecore Rocks extensions were overhauled... And Hedgehog (more precisely TDS's main mastermind, Charlie Turano) worked closely with Sitecore (namely Sitecore Rocks' main mastermind, Jakob Christensen) to have the connector continue to work. Minor updates were made, and developers continued to benefit from these two great tools working seamlessly together. Then in 2014, TDS v5.0 was released. One of the new features that Mike Edwards created, and demoed here was a new set of contextual options that utilize the TDS <=> Rocks connector. (Jump to 24:40 to see this in action) This reduced round-trips between Rocks and TDS content trees for manually synced items. Filling the gap between AutoSync'd items, and new ones to be AutoSync'd that were previously excluded. Fast forward to now.... March of 2016, and TDS v5.5 is about to be released with 'AutoSync'. So item changes in Sitecore are automatically pulled into the TDS project. A great feature.... but really I see it as the existing AutoSync that's been around for 5+ years...just with added browser support. OK.... not all developers use Sitecore Rocks.... sometimes you just want to use Sitecore in the browser. Now TDS's AutoSync can be switched on, and the same auto-updating in your TDS project can take place. With that said.... I don't mean to down-play this feature at all. I too use the browser on occasion.... and even with the TDS <=> Rocks connector installed I can turn on this new AutoSync feature, and have everything automated for me, both from within Visual Studio, and from within Chrome/Firefox/Edge/IE?/Opera?.... It's time to Automate All the Things! and TDS v5.5 enables this with the new version of AutoSync. Charlie has done an amazing job with this feature... making it seamless, and minimally intrusive to the Sitecore instance. To get it that way, he's done amazing work... so me saying it's 'just added browser support' hopefully doesn't take away from that. :-)

Sitecore Development

Related Blog Posts

Azure Sitecore Deployment: Deploying to a Slot
Setting up Azure staging slots, so the next release of our project can be placed there, allows us to deploy the new code to a private website (the slot), and test it before pushing it live. We are going to script this process to make it easier for the devops team to automate.
TDS Classic Best Practices: NuGet Build Components and TDS Classic .user configs
There are certain systems and processes that you can put in place to make a TDS Classic project run more smoothly. We're highlighting the best practices that our team recommends for getting the most out of TDS Classic.
Azure Sitecore Deployment: Adding Project's Code and Items to the Azure Deployment
Modify the scripts so that the compiled LaunchSitecore site is also provisioned into the new XP environment.
TDS Classic Best Practices: Bundle Packages, Delta Builds and Delta Packages
Following TDS Classic best practices, like using Delta Builds and Delta Packages, can make the entire development experience run much more smoothly.
Azure Sitecore Deployment: Adding Custom Modules
Modify the previous install so that the initial install contains the Sitecore Package Deployer module. It is an excellent way to enable continuous integration to the website.
TDS Classic Best Practices: Validators and the Sitecore Package Deployer
TDS Classic can be used in many ways, but the goal is always the same: make development (and developers lives) easier. Whether it's using the Sitecore Package Deployer or using validators, following best practices can make your entire experience run much more smoothly.
Azure Sitecore Deployment: Preparing the Default Scripts and Packages
Preparing the default packages for a Sitecore Azure deployment and extending to add a custom module to the install.<br> <br> <br> <br> <br>
Azure Sitecore Deployment: Setting Up the Solution and VSO Build
<p>The first in our series on setting up a Sitecore instance on Azure, with an initial deployment that includes custom built modules as add-ons to the setup.</p>
Troubleshoot and Prevent Failed TDS Classic Project Builds
When building an .update package with TDS Classic, the build might fail with no additional information. From increasing log verbosity to using validators, there are ways to minimize or prevent this type of error.
TDS Classic How-To: Disable Automatic Code Generation
Code Generation is automatically triggered after every change in the TDS Project tree. If a project contains many items, users can disable this feature for their convenience.
TDS Classic Sitecore Deploy Folder
Sitecore Deploy Folder is a setting, located in the build tab of the TDS Classic Project's Properties page, and used to tell TDS Classic where the webroot is located.<br>
TDS Classic Builds on Jenkins Build Server with NuGet Packages
Our simple scenario includes 2 developers using TDS Classic and checking-in changes to source control. The Jenkins build server takes the changes and performs the build, and then deploys the created package to two Sitecore environments.
Features to Improve Sitecore Development: TDS Classic Strikes Back
Each and every feature in TDS Classic is aimed at helping developers. Whether the feature is out front or running quietly in the background the goal is always the same: make the development experience better. &nbsp;&nbsp;
Feydra and the Virtual Sandbox
Feydra virtualizes all front end assets (css, js &amp; cshtml) of a Sitecore instance. With Feydra, front-end developers can commit their changes to Source Control without requiring the intervention of a back-end developer. We call it a virtual sandbox.&nbsp;
Feydra Frequently Asked Questions
Answering a number of excellent questions we've gotten from the community regarding Feydra, including how long it takes to set up a Feydra environment and how to install the product.&nbsp;
TDS Classic Features to Improve Sitecore Development
Each version of TDS Classic comes with the same goal: to make Sitecore development and, by extension, developers, lives easier. Every feature in our products is aimed at making the process better - some of these features aren't quite as well-known as others, but they all help smooth and improve the development experience.
Deployment Properties and the Deployment Property Manager
When working with TDS Classic, you will eventually need to deploy your items to a Sitecore instance and you might not want the default behavior of every item in your TDS project deploying every time. This is where the TDS Sitecore Deployment Property Manager comes in!
Feydra: A Front-End Assessment
Feydra allowed me to start building the front-end in a very short time with no Sitecore experience, and it let me use tools that I was comfortable and familiar with.
Feydra: A Quick Start Guide
A step-by-step guide for installing, configuring and, most importantly, using Feydra from the front-end.
TDS Classic 5.6 Feature Spotlight - Prevent Deployment of Incorrect Assemblies
This feature, new to TDS Classic 5.6, will prevent a solution from deploying unless all assemblies (except the excluded assemblies we allow you to specify) match what exists in your webroot.&nbsp;
Feydra from the Front-End
Feydra eliminates common roadblocks for designers and front-end developers working on Sitecore projects by getting them up and running more quickly and allowing them to use the development environment and workflow tools they prefer.&nbsp;
TDS How To: Install the TDS Connector for Rocks 2.0
Manually install the TDS connector for Sitecore Rocks 2.0
Using NuGet Packages in TDS
New to TDS 5.5 is the ability to create and consume NuGet packages in your TDS project, allowing developers to capture their Sitecore items and easily distribute them across multiple teams.
Occasional Issue Seen with TDS Installer
When upgrading to TDS 5.5.0.x from an older version and trying to load a solution with a TDS project inside, the following error might occur:
TDS for SC Hackathon 2016
For all those participating in the Sitecore Hackathon, check out our Habitat for TDS and some other cool surprises.
Config Transforms for Config Files
If you don't want to use a third party development tool for your config transforms, I have good news. Config transforms are supported natively within TDS!
Package Installer from the Command Line
The TDS package installer allows you to install packages through the command line. Learn how...<br>
New Build for TDS 5.0!
A couple bugs were reported over the last few months. We've been able to fix the bugs and now have a stable CTP version for use.
It's finally here!
Team Development for Sitecore has finally been released go download it now!
Team Development for Sitecore Webinar
Our Sitecore MVPs Charlie and Sean recently did a demo of TDS to all Sitecore partners. We recorded the demo to share with the world.