Blog

A Look Back at TDS Classic

March 14, 2019 | Hedgehog

TDS Classic has been helping Sitecore developers improve team integration and smooth the development process for 10 years. Sitecore Solution Architect and Chief Product Scientist, Charlie Turano speaks about the beginning of TDS and where it is today. 

First things first, what is TDS Classic (TDS)? 
TDS is a tool we developed from our internal tools. It’s a tool to optimize the development process for building a Sitecore website.

How did you come up with the idea for TDS?
A lot of it came from looking at the way we developed websites before Sitecore. I took a step back and saw how we managed source code.While thinking about how .Net websites were developed without Sitecore, I realized Sitecore items are source code too. This led me to the basic concept of TDS: bringing Sitecore items into Visual Studio just like a code. 

How did you feel when the first version of TDS was launched? 
I wasn’t sure what would happen. We didn’t know what we had at the time. We were thrilled with the first license purchase, but we were unsure if TDS would go anywhere. We started to gain traction about 6 months after the release. That’s when we knew we were onto something. 

How do you develop new features for TDS?
I look for ideas in three places: support, talking to Sitecore MVPs and Sitecore Developers, and my own experience. I read every email that comes through the support inbox. If I notice a recurring theme, I think about how I can address the issue. I ask Sitecore MVPs what issues they are experiencing, and how can I make their development process better? Lastly, my experience working in Sitecore helps me because what frustrates me might be frustrating other developers. I look for ways to reduce the frustration for all Sitecore developers.

What have been some of the biggest challenges you faced as you developed TDS throughout the years? 
The biggest challenge is taking a specific problem and generalizing it. I have to think about how does this problem relates to everyone, not just the specific issue we are trying to solve. I work with Sitecore and Hedgehog employees to create a solution for a class of problems instead of a specific solution.

TDS 5.8 has recently been released. What was your biggest accomplishment while working on TDS 5.8? 
Setting up Azure deployments with TDS. Roughly 70% of the development time was spent trying to figure out how to properly connect TDS with Azure.

Looking back ten years ago, did you imagine the Sitecore community embracing TDS the way they have?
Not at all – again we didn’t know what we really had at the time. I am pleased with the way the Sitecore community has embraced it.

Were there alternate name ideas for TDS?
No, it was straight forward when it came to naming TDS.

Have you personally developed every version of TDS to date? 
Yes, it has mostly been me. We have had other developers work on pieces of the code, but I'm involved in every release. When we have betas we also elicit feedback from developers to make sure the product works as it should in the “real world”.

What has been most rewarding about bringing TDS to the Sitecore community?
It must be going to a symposium, sitting in an audience and seeing presenters doing presentations with TDS Classic in their Visual Studio solutions. It's like wow, I wrote that!

Charlie works out of Hedgehog’s Holbrook, New York Headquarters. You can connect with him through LinkedIn. 

 

TDS Classic Charlie Turano TDS Classic 5.8

Related Blog Posts

Hedgehog Announces the Release of TDS Classic 5.8
Hedgehog announced the release of TDS Classic 5.8. The newest update now supports Azure and Visual Studio 2019.
TDS Classic Licensing FAQ
Answers to a number of frequently asked questions regarding the licensing of TDS Classic.
The Benefits of Renewing a TDS Classic License
New features and early access to the latest and greatest in the Essential Collection are just a few reasons to keep your TDS Classic license active.
Guide to Sitecore Packaging
Development of features and components requires a set of Sitecore items to be packaged - things like renderings and templates. With TDS Classic, Sitecore developers can automate the packaging process. 
TDS Classic as a Tool for Technical Audits
TDS Classic provides Project Report generation for Sitecore items, which can be very helpful with technical audits
Razl 4.0: Compare Editors for Complex Fields
Razl 4.0 introduces a new function for comparing and moving complex field values in Sitecore, which makes determining the differences between fields on an item much simpler.
TDS Classic: Content File Sync
Content File Sync is a fantastic time saver for any Sitecore developer.
Razl 4.0: Multi-Threaded Copy
Razl 4.0 has enhanced the function to copy items and sub items from one database to another to allow more than one items to be copied at once, which dramatically improves the performance of copy operations.
TDS Classic How-To: Perform Unattended Installation of TDS Classic for Visual Studio 2017
The TDS Classic version for Visual Studio 2017 is installed a bit differently than previous versions; the process is separated in two parts and performed by two different installers.
TDS Classic 5.7 - Lightning Deploy
Lightning Deploy Mode can be used to enable Lightning Mode for all deployments that utilize the TDS Sitecore Connector in their configuration, improving their speed and efficiency.
TDS Classic 5.7 - Lightning Sync
Lightning Sync allows both sync and quick push operations to use TDS Classic 5.7's new Lightning Mode feature
TDS Classic 5.7 - Solution Wide Sync
A simple new feature in TDS Classic 5.7, Solution Wide Sync makes a big difference when working with many TDS Classic projects in a solution.
TDS Classic 5.7 - Lightning Mode
Lightning Mode helps to improve the speed and efficiency of both deploy and sync operations. This enhancement is achieved by modifying how item comparisons are performed.
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.
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.
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.
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;
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!
TDS Classic How-To: Use the HedgehogDevelopment.TDS NuGet Package
The HedgehogDevelopment.TDS NuGet Package allows you to build TDS projects, without the need of installed TDS on the build server machine.
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;
TDS 5.6 Feature Spotlight - Project Item Report
This feature, new to TDS Classic 5.6, allows you to create a report of all items in the TDS Classic project.&nbsp;
Create TDS Classic Custom Post Deploy Step
Team Development for Sitecore Classic version 5.5 allows developers to add post deployment steps to to their deployments and update packages. TDS Classic has used post deployment steps internally to perform a number of useful functions. Many of the developers using TDS Classic have requested the ability to add their own post deploy functionality. With the release of TDS Classic 5.5 in early 2016, this functionality is now available.