TDS Blog: Sitecore Best Practices and Dev Insights
June 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.
TweetMarch 20, 2017 | Kliment Klimentov
TDS Classic is pushed to the build server in the NuGet package. The build server then restores the package and uses the files from the package to build the TDS Classic Projects in the solution, instead of using files from the installed TDS Classic.
TweetNovember 30, 2016 | Kliment Klimentov
Create .update package with TDS, using dll files from the Sitecore NuGet repository
TweetOctober 14, 2016 | Kliment Klimentov
Item sync (Sync with Sitecore or Get Sitecore Items) is normally a fast process; it shouldn’t take more than a few seconds. However, the speed of item sync depends on both the environment TDS is working with and the volume of items. First, check to see whether there is a problem with the Sitecore log.
Tweet