When usync exports and imports macros, it doesn't sync the Guids. This is causing problems where when we try to courier content that is dependent on any macros, Courier believes the two macros to be different macros because their Guids are different.

I have reproduced this problem on two sites so far

site 1:

• Umbraco: 7.7.9
• Courier 3.1.6
• uSync: 4.0.2
• uSync.Core: 6.0.2

site 2:

• Umbraco: 7.13.1
• Courier 3.1.5
• uSync: 4.0.10
• uSync.Core: 6.0.10

This is an example of some of the xml that uSync is exporting for a macro called "Test Macro" with this guid: 24191f38-0134-440c-8eef-3d7b2e17eea8

<?xml version="1.0" encoding="utf-8"?>
<macro Key="00000000-0000-0000-0000-000000000152">
  <name>Test Macro</name>
  <alias>TestMacro</alias>
  <scriptType></scriptType>
  <scriptAssembly></scriptAssembly>
  <scriptingFile>~/Views/MacroPartials/TestMacro.cshtml</scriptingFile>
  <xslt></xslt>
  <useInEditor>True</useInEditor>
  <dontRender>False</dontRender>
  <refreshRate>0</refreshRate>
  <cacheByMember>False</cacheByMember>
  <cacheByPage>False</cacheByPage>
  <properties />
</macro>

In the above xml, the macro Key does not have the correct Guid. When we import this macro into the site in a different environment, the macro will have a different guid in each environment (ex. 66567bc5-7710-47e5-a8ca-ad2c0d660422). If we put any of these macros into a rich text editor, Courier will pick up the macro as a dependency, attempt to deploy it, and run into naming collisions.

This has definitely been working for us for quite a while. I am only now noticing the problem. Did something change in the way that macros are handled recently? Are we misconfiguring something?

Thanks. Let me know if you need more details.