Blog
July 12, 2018 | Phil Mattox
TDS Classic is licensed per developer and can therefore be installed on your Build Server, multiple machines, and environments at no extra charge. Each team member using TDS Classic must have their own license to utilize the software. Each initial purchase of TDS Classic includes a free year of maintenance and support; after the first year there is an annual renewal fee of 40% of MSRP.
A TDS Classic license must be renewed or extended on or before its expiration date to keep the benefits of the Maintenance and Support agreement active (and to take advantage of the renewal rate – once a license expires it will be necessary to purchase a new license to reactivate the benefits). An expired license means risking compatibility with other required programs such as Sitecore and Visual Studio, and security risks may apply depending on your configuration.
Maintenance
New TDS Classic features and enhancements are released at least twice a year to ensure maximum compatibility with Sitecore, Visual Studio, Source Control, and build server products as they improve. They also include bug fixes and security patches.
Support
Our world class Support Team is not only here to assist with any TDS Classic issue or question, but is also available for project guidance and product tips to ensure peak efficiency.
Email newsletter
Once a month we send out an email newsletter containing the latest thought-leadership on TDS Classic, as well as tips, tricks, updates, and announcements for all the products in our Essential Collection. This email is an exclusive benefit for active license holders, and is often the first place that useful content is available to the public.
Early access to new products and beta releases
We want our clients to be the first to try new software offerings; renewing your license keeps you on the list for early access and beta testing licenses.
We do offer discounts for bulk purchases, including enterprise license options for 40 seats or more. Non-profit organizations and Sitecore MVPs are eligible for discounts as well. To request discounted pricing, please contact us directly.
Still have questions? Reach out to our Sales team or visit our FAQ page for more details regarding TDS Classic Renewals.
Tags
- TDS Classic goes to Australia
- Hedgehog Solution Architect, Sean Holmesby will be presenting at SUGCON ANZ. He gave insight on his topic and more.
- TDS Classic to Support Rainbow
- <p>At SUGCON London, Sitecore announced they would be switching over their default serialization format to Rainbow, a YAML-based format for Sitecore serialization in Sitecore version 9.2., and TDS Classic is ready to support it. </p> <div> </div>
- What is New in TDS Classic 5.8?
- We go over the new features in TDS Classic 5.8 that can help significantly improve your experience.
- Setting Up TDS 5.8 to Build to Azure Using Visual Studio Build and Pipelines: Configuring Azure DevOp's Release Pipeline
- In this part, we are configuring the setting in the Release pipeline to deploy our Web Deploy package.
- Setting Up TDS 5.8 to Build to Azure Using Visual Studio Build and Pipelines: Configuring Azure DevOp's Build Pipeline
- In this part, we'll configure only the steps in the Build Pipeline, and publish the build drop (a Web Deploy package and a PowerShell script) to the Release pipeline.
- Setting Up TDS 5.8 to Build to Azure Using Visual Studio Build and Pipelines: Local Set Up
- By using TDS 5.8 and Web Deploy packages, we'll show you how to create a fully automated build and deployment process from your workstation to source control and into your Azure environment.
- A Look Back at TDS Classic
- TDS Classic has been helping Sitecore developers for 10 years. We spoke with Sitecore Solution Architect and Chief Product Scientist, Charlie Turano to reflect back on the making TDS Classic.
- 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.
- 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
- TDS Classic: Content File Sync
- Content File Sync is a fantastic time saver for any Sitecore developer.
- 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.
- 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.
- 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.
- 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.