New Build for TDS 5.0!

March 26, 2014 | Mike Shaw

We have heard tons of great feedback from our adopters and are excited to say we are in the final stages before our release! We anticipate making a release announcement in the next week, so keep an eye out!

We have done a build to fix a couple issues that you’ve brought to our attention. Here are the changes we’ve made:

  • Re-enable the global config menu item if the global config gets deleted – An issue was reported that was when a global config file was deleted the menu item became disabled. Now even when the global config file is deleted the menu item gets re-enabled, not affecting your solution.
  • The “Get Sitecore Items” window duplicate detection is case sensitive – When you had duplicate items in your project and ran the duplicate item detector it was not picking up letters with different cases. We resolved this issue by telling TDS to ignore case when making this detection.
  • Slow Project Loading – When a TDS project was being loaded for the first time, it took Visual Studio a few minutes to load the project.  The first time none of the items exist in the Sitecore instance. This causes an exception to be thrown in SitecoreIconCache line 96. However because the exception contains the words "not found" the cache failure time is not set. This means that for every item added to the project TDS, it has to request not only the icon for the current loading icon, but the icon for all other items at that level in the project. If they don't exist it causes a massive overhead.
  • Cleanup whitespace in file – When we were generating TT files, there was white space being made in the middle of the file. This whitespace was not appealing to many developers. We changed the protocol to not create whitespace during TT file generation.
  • Change the load order of the Microsoft.Web.Publishing.Tasks.dll - Currently, we search for the Microsoft.Web.Publishing.Tasks.dll by looking for the older versions first. This may cause problems if new features are released by MS for transformations. Trying to load the 2013 version of the dll into VS2010 may fail. We have switched the load order to help ensure acceptance of new features.


We’ve done a build with all these fixes that you can currently download.  If you experience any issues make sure to email us (  Also, make sure to keep an eye out for our official release date announcement!


Related Blog Posts

Enhanced Content Editing for Sitecore: An Avtor Live Chat
In our first product-entered live chat, the team covers Avtor, the essential Sitecore content editing tool
Hedgehog Announces Release of Avtor
Hedgehog, a digital consultancy engineering high - performance, multi-channel solutions, today announced the release of a brand-new product called Avtor, a part of the Team Development for Sitecore Essential Collection.
How Feydra Improves Front-End Development for Sitecore
Feydra offers a more efficient modern approach to front-end development workflow for Sitecore.
Guide to Sitecore Packaging
Development of features and components requires a set of Sitecore items to be packaged - things like renderings and templates. With TDS Classic, Sitecore developers can automate the packaging process. 
TDS Classic: Content File Sync
Content File Sync is a fantastic time saver for any Sitecore developer.
Azure Sitecore Deployment: Deploying to a Slot
Setting up Azure staging slots, so the next release of our project can be placed there, allows us to deploy the new code to a private website (the slot), and test it before pushing it live. We are going to script this process to make it easier for the devops team to automate.
TDS Classic Best Practices: NuGet Build Components and TDS Classic .user configs
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.
Azure Sitecore Deployment: Adding Project's Code and Items to the Azure Deployment
Modify the scripts so that the compiled LaunchSitecore site is also provisioned into the new XP environment.
TDS Classic Best Practices: Bundle Packages, Delta Builds and Delta Packages
Following TDS Classic best practices, like using Delta Builds and Delta Packages, can make the entire development experience run much more smoothly.
Azure Sitecore Deployment: Adding Custom Modules
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.
Azure Sitecore Deployment: Preparing the Default Scripts and Packages
Preparing the default packages for a Sitecore Azure deployment and extending to add a custom module to the install.<br> <br> <br> <br> <br>
Azure Sitecore Deployment: Setting Up the Solution and VSO Build
<p>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.</p>
Troubleshoot and Prevent Failed TDS Classic Project Builds
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.
TDS Classic How-To: Disable Automatic Code Generation
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.
TDS Classic Sitecore Deploy Folder
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.<br>
TDS Classic Builds on Jenkins Build Server with NuGet Packages
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.
TDS How To: Install the TDS Connector for Rocks 2.0
Manually install the TDS connector for Sitecore Rocks 2.0
Using NuGet Packages in TDS
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.
Occasional Issue Seen with TDS Installer
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:
TDS: The Evolution of Auto-Sync
Auto-Sync has been described as a new feature, but in reality has existed in TDS since 2010 and has taken a new form in TDS 5.5, due to be released March 22, 2016
TDS for SC Hackathon 2016
For all those participating in the Sitecore Hackathon, check out our Habitat for TDS and some other cool surprises.
Config Transforms for Config Files
If you don't want to use a third party development tool for your config transforms, I have good news. Config transforms are supported natively within TDS!
Package Installer from the Command Line
The TDS package installer allows you to install packages through the command line. Learn how...<br>
It's finally here!
Team Development for Sitecore has finally been released go download it now!
Team Development for Sitecore Webinar
Our Sitecore MVPs Charlie and Sean recently did a demo of TDS to all Sitecore partners. We recorded the demo to share with the world.