Blog

TDS 5.6 Feature Spotlight - Project Item Report

February 15, 2017 | Joe Hicks

This new feature in TDS 5.6 will allow you to create a report of all items in the TDS project. At this time, users can export two different formats, Markdown and XML, but we can add more if the need is there.

Keep in mind the markdown report compatibility may vary from application to application since there is no 100% standard format, but the markdown report is compatible with the Visual Studio 2015 markdown editor add-in. Different types of Items will have different output that will show in the report.

• Templates: Base templates, inheritance, icons and fields in standard values for templates, workflow, template and field validators
• Sublayouts/Renderings: Compatible renderings, thumbnails, placeholders in the rendering, file paths.
• Placeholder Settings: Renderings for a placeholder

You can change the settings for this report in the “Project Report” tab of your TDS project. Here you will find the checkbox to enable/disable the report generation, as well as what type of report (xml/markdown), Report Name, as well as an option to add additional fields (we will get to that shortly). You are able to search for fields to add as well.

TDS Classic 5.6 Project Report Tab

Here is a sample of the xml output for our test site that includes a few sample items as well as a sample rendering.

TDS Classic 5.6 Project Item Report Sample Rendering

One thing you’ll notice is that the path is included. We also include a sample XSL Transform you can use to render the xml in a browser that can be modified to
fit your needs.

There are several new features in TDS Classic 5.6 that are geared, just like Project Item Report is, toward improving developer productivity. Check out the post on Quick Push, or just skip to the best part and download TDS Classic 5.6 today

TDS 5.6 TDS Classic TDS Classic 5.6 features

Related Blog Posts

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.
Features to Improve Sitecore Development: TDS Classic Strikes Back
Each and every feature in TDS Classic is aimed at helping developers. Whether the feature is out front or running quietly in the background the goal is always the same: make the development experience better. &nbsp;&nbsp;
TDS Classic Features to Improve Sitecore Development
Each version of TDS Classic comes with the same goal: to make Sitecore development and, by extension, developers, lives easier. Every feature in our products is aimed at making the process better - some of these features aren't quite as well-known as others, but they all help smooth and improve the development experience.
Deployment Properties and the Deployment Property Manager
When working with TDS Classic, you will eventually need to deploy your items to a Sitecore instance and you might not want the default behavior of every item in your TDS project deploying every time. This is where the TDS Sitecore Deployment Property Manager comes in!
TDS Classic How-To: Use the HedgehogDevelopment.TDS NuGet Package
The HedgehogDevelopment.TDS NuGet Package allows you to build TDS projects, without the need of installed TDS on the build server machine.
TDS Classic 5.6 Feature Spotlight - Prevent Deployment of Incorrect Assemblies
This feature, new to TDS Classic 5.6, will prevent a solution from deploying unless all assemblies (except the excluded assemblies we allow you to specify) match what exists in your webroot.&nbsp;