Skip to content
DD4T Core delivery framework for Microsoft.NET
Branch: develop
Clone or download

Latest commit

Latest commit 8838473 Dec 31, 2019


Type Name Latest commit message Commit time
Failed to load latest commit information.
configuration preparing for release 2.5 Dec 20, 2019
source preparing for release 2.5 Dec 20, 2019
.gitignore added .vs folder to ignore Apr 6, 2018
DD4T Core.Targets cleaned up debugging messages Dec 17, 2019
LICENSE Initial commit Feb 27, 2015 Update Dec 31, 2019
appveyor.yml build number back to alpha [nobuild] Dec 20, 2019
build.msbuild Renamed Solution File to DD4T.Core Jun 2, 2016




DD4T - delivery framework for Microsoft.NET

Release notes for version 2.5

This release rolls up the bugfixes and stabilization and performance improvements that have been released in the various DD4T NuGet packages over the last years.

This release contains new versions of:

  • All NuGet packages that make up the .NET version of DD4T
  • The Tridion templates
  • The dd4t-cachechannel.jar (which is needed to invalidate items in the DD4T cache when they are republished or unpublished)

The Java version of DD4T is not included in this release. If you want to use DD4T in a Java web application, please use version 2.1.5. However, this version does not include support for the page regions that were introduced by SDL in SDL Tridion Sites 9.0. You can use this version in combination with the 2.5 templates.

Features / improvements introduced in this release

  • Full support for regions in Tridion 9 (see below).
  • Cache invalidation is now working properly with SDL Web 8.5 as well as Tridion 9.0 / 9.1 (see for installation notes).
  • Cache invalidation now removes all dependencies on a Tridion page or component, including indirect dependencies like models
  • Cache invalidation also works for component links now. This means you can cache them for much longer. To do that, add <add key="DD4T.CacheSettings.Link" value="3600" /> to your Web.config. The value is in seconds, so this would cache links for 1 hour, but you could cache them for longer if you want because they are invalidated anyway.
  • Metadata fields on pages and templates work even if they are annotated without 'IsMetadata=true'.
  • Experience Manager implementation was optimized. You can now load the page bootstrap code (including the HTML comments required to identify the page) with the following command:
    It is also possible to make fields in linked components editable, by using this command in your Razor views: @Model.Link.StartXpmEditingZone(Model)
    (assuming the property 'Link' points to a linked component).
  • Added missing DependencyMapper classes to all providers so they can now all be loaded automatically.
  • Upgraded Newtonsoft.Json to 11.0.2 for all DD4T projects

Bugs fixed in this release

Getting started with DD4T

If you want to start using DD4T yourself, please check out the Wiki.

Regions in Tridion 9

Before the introduction of page regions in Tridion 9, the concept of 'regions' of component presentations on a page was commonly implemented using a metadata field called 'region' on the metadata of the component template. In that case, the web application would group component presentations together based on this metadata field.

With DD4T 2.5 you can now upgrade your CM to Tridion 9 / 9.1 and start using regions, without having to change your web application. All you need to do is add the new template building block 'Convert regions to CT metadata' to your page templates. It will put a metadata field called region in each of the component templates, and put the name of the region in it.

You can’t perform that action at this time.