locked
CU1 breaks custom transport agents built for RTM RRS feed

  • Question

  • After CU1 is applied, custom transport agents built for RTM cannot be loaded and the transport service does not start successfully.

    Why this happens is known (please see http://blogs.msdn.com/b/akashb/archive/2010/11/19/getting-an-error-when-trying-to-install-a-transport-agent-that-is-built-with-exchange-2010-pre-sp-1-binaries-on-exchange-2010-sp-1.aspx for more information).

    My question is: When will MS do its homework and implement and deploy assembly redirection policies with any upgrade which contains new public assemblies, like CU1.

    In MXS 2007 and 2010, assembly redirection policies were correctly implemented, meaning that custom transport agents built against the MXS 2007 public assemblies worked on all MXS 2007/2010 releases, no matter which SP.

    Does MS really expect 3rd-part vendors to release new versions of their products quarterly, some days after release of the next CU, while in the meantime customers have to deactivate the vendor's SW till the new version is available?

    I assume that the omission of assembly redirection policies was just an accident...

    Can please someone from MS provide information about when a solution regarding the missing assembly redirection policies can be expected?

    Thanks in advance!

    Monday, April 15, 2013 5:07 PM