TDS Blog: Sitecore Best Practices and Dev Insights
October 06, 2016 | Kliment Klimentov
Manually install the TDS connector for Sitecore Rocks 2.0
TweetSeptember 20, 2016 | Kliment Klimentov
If you want to move your Sitecore development environments to newer version of Visual Studio, you will first need to install the new VS version you have selected. Then download TDS from our website. We recommend using the latest version of TDS as it has the latest features and is compatible with all previous versions, but...
TweetSeptember 05, 2016 | Kliment Klimentov
With TDS you can delete items from the Sitecore tree, using an update package. The Recursive Deploy action controls how TDS responds to Items in the target Sitecore instance, but not existing in the project.
TweetAugust 02, 2016 | Kliment Klimentov
When using Visual Studio on a restricted machine, a scenario may manifest wherein TDS can’t be installed on the default location (MSBuildExtensionsPath = C:\Program Files (x86)\MSBuild). As a consequence, the TDS .targets import setting inside the .scproj files () are not valid. In order to work around this restriction, one can add the path …
TweetJuly 20, 2016 | Kliment Klimentov
TDS gets the item icons from Sitecore. If there is an issue connecting to the website during the download process of the items, some icons may default to the following (on the left): If that happens, it is possible to force TDS to get the icons again by deleting the /obj/IconCache folder.
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:..
Tweet