Skip to main content

Which AddBinary (not) To Use?

If you look at the CHM documentation for TOM.NET, you will see a plethora of AddBinary methods and their  overloads. Why so many? I don't know, maybe for flexibility...

While some of them are clearly marked as 'internal', some are deprecated and the rest are just out there. So which ones to use? Well, the story is a bit longer here. Clearly, don't use those marked as 'internal'. However, the deprecated (or actually Obsolete) methods are the tricky ones. It seems they are only deprecated since Tridion 2011SP1, while in fact they are buggy. Different behaviors have been reported on them -- binaries becoming un-managed once published. This means, a Unpublish action would leave that binary behind on the Content Delivery side.

So which are the safe to use AddBinary methods?
  • In Tridion.ContentManager.Publishing.Rendering.RenderedItem:
    • AddBinary(Component);
    • AddBinary(Component, String);
    • AddBinary(Component, StructureGroup);
    • AddBinary(Component, StructureGroup, String);
    • AddBinary(Stream, String, String, Component, String);
    • AddBinary(Stream, String, StructureGroup, String, Component, String);
  • In Tridion.ContentManager.Templating.Engine:
    • AddBinary(TcmUri, TcmUri, TcmUri, Byte[], String);

Which AddBinary NOT to use:
  • In Tridion.ContentManager.Publishing.Rendering.RenderedItem:
    • AddBinary(Stream, String, String, String); - obsolete
    • AddBinary(Stream, String, StructureGroup, String, String); - obsolete
  • In Tridion.ContentManager.Templating.TemplatingRenderer:
    • AddBinary(TcmUri, TcmUri, TcmUri, Byte[], String); - use Engine.AddBinary instead


Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: I stumbled upon the following post from 2008 (!!!), , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a