TDS Blog: Sitecore Best Practices and Dev Insights
July 26, 2017 | Charlie Turano
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.
TweetJuly 19, 2017 | Kliment Klimentov
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.
TweetJuly 17, 2017 | Charlie Turano
Preparing the default packages for a Sitecore Azure deployment and extending to add a custom module to the install.
July 14, 2017 | Charlie Turano
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.
TweetJune 01, 2017 | Kliment Klimentov
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.
TweetMay 23, 2017 | Kliment Klimentov
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.