We have a custom resolver that adds all Keyword metadata linked Components when a Category is published. We've compiled our resolver and altered the Tridion.ContentManager.config to utilise:

<add itemType="Tridion.ContentManager.ContentManagement.Category">
        <add type="CustomerResolvers.CategoryResolver" assembly="CustomerResolvers" />

This correctly returns the Category, and all linked DCPs, but only locally, or on our test server. Our dev server only returns the Category. On dev, it seems to be doing something, as logging shows that it finds the linked Components. They just aren't listed when you click Show items to publish.

Both dev/test have the same content, and the same version of Tridion. I didn't set up the servers, so I'm wondering if anyone has any idea as to why the different behaviour? I'm not ruling out stupidity, but have run out of ideas.

  • Can you confirm the same version of the DLL (CustomerResolvers) is available and configured on both environments (including on all Publishers and possible outscaled CME servers)? Commented Jun 7, 2017 at 13:23
  • Yes, same version. Each server has publisher service running locally. Commented Jun 7, 2017 at 14:46
  • Which version of Tridion? I think the "show items to publish" thing only triggers custom resolvers as of 2013 (or maybe there was a defect in some version where this didn't work)
    – Nuno Linhares
    Commented Jun 7, 2017 at 14:55
  • Update Version: Hotfix Rollup SDL Tridion 2013 SP1 - 1 Commented Jun 7, 2017 at 14:59
  • 1
    Are the same DCPs published in both environments (i.e. the environment(s) you're resolving to)? Commented Jun 8, 2017 at 13:11

2 Answers 2


Can you try attaching to the process and debugging it? Do note that if the deployed dll is different than the code you've put the breakpoint in, the breakpoint won't be hit. Also, for this you need to deploy a debug build of the resolver.


I said not to rule out stupidity. On the dev server, the component template was not configured for a dynamic component presentation. The custom resolver would not have included the required DCPs.

In my defence the nature of the remote server access means I have to set this up manually. I guess I could keep generating Content Porter packages, but that's another world of pain.

  • Glad you found the problem. Might I suggest that you accept your own answer so this question "becomes closed"?
    – Atila Sos
    Commented Jun 8, 2017 at 17:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.