July 19, 2017 | Kliment Klimentov
TDS Classic can be used in a variety of ways depending setup and infrastructure. It can be used with or without build server, deploying directly, or using packages; it's all up to the user and their needs. And whether it's using the Sitecore Package Deployer or using validators, following best practices can make the entire experience run much more smoothly.
Avoid adding content and media items
We recommend that users avoid adding content and media items into TDS Classic projects. Doing so can cause long deployment times and even timeouts. If media and content items need to be added to the TDS Classic project, it's good practice to create a separate project for that purpose while being careful not to overwrite editor's content.
Use validators to catch problems earlier
We also recommend using validators to catch problems in items or environment problems, such as catching issues with invalid characters in item fields. TDS Classic Validators ensure the deployment properties in the TDS Classic project are correct.
Use the Sitecore package deployer to install .update packages automatically
When setting up Continuous Integration, it is possible to make the package installation easier by using our open-source Sitecore Package Deployer. The Sitecore Package Deployer installs packages automatically when they are pasted in a certain folder, and makes CI processes easier to implement.
Be careful with the automation of the Sitecore deployment process
Direct TDS Classic deployments should only be done on lower tier, non-crucial environments like Dev Integration and QA. For Staging and Production, we recommend using a manual or semi-automatic deployment method using TDS Classic update packages.