TDS Blog: Sitecore Best Practices and Dev Insights
August 09, 2017 | Kliment Klimentov
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.
TweetAugust 02, 2017 | Kliment Klimentov
Following TDS Classic best practices, like using Delta Builds and Delta Packages, can make the entire development experience run much more smoothly.
TweetJuly 11, 2017 | Kliment Klimentov
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.
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.
May 10, 2017 | Kliment Klimentov
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.
Tweetsitecore (×)