TDS Blog: Sitecore Best Practices and Dev Insights
May 31, 2016 | Angel Uzunov
In any normal course of a project’s lifecycle a developer could have any number of TDS projects inside the solution. In order to increase productivity (IE we are too lazy to do the same thing twice) it makes sense to share build configurations between the projects. We released this ability with the Global Config File...
TweetMay 27, 2016 | Charles Turano
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.
TweetMay 26, 2016 | Kliment Klimentov
There is no worse feeling than a broken build. OK maybe that is an exaggeration but broken builds can be really soul crushing. When trying to use TDS on a build server deployment, the build might fail with the following error: “warning MSB3644: The reference assemblies for framework “.NETFramework,Version=v2.0” were not found” and “error MSB3645:..
TweetMay 10, 2016 | Angel Uzunov
Proxy servers are widely used in the enterprise to facilitate security, administrative control or caching services. TDS can be configured to work behind a proxy server.
TweetMay 03, 2016 | Charlie Turano
New to TDS 5.5 is the ability to create and consume NuGet packages in your TDS project, allowing developers to capture their Sitecore items and easily distribute them across multiple teams.
TweetApril 28, 2016 | Kliment Klimentov
When upgrading to TDS 5.5.0.x from an older version and trying to load a solution with a TDS project inside, the following error might occur:
Tweet