This content has been archived.

How do I handle custom assembly references?

Typically, you would include custom assembly references when you want to use custom logic in the solutions you build.

Note: Studio version resolves an issue which could occur when you use custom assembly references in your automations. Installing version or higher resolves the issue for any new solutions you create. If, however, you upgrade existing solutions to this version, you may still encounter this issue.

Here is an example:

Custom references example

Prior to version, the highlighted line is only copied to the first automation to which the custom component is added. Other automations that use this custom component will not contain this line. If the first automation is deleted, all of the other automations will throw errors because they do not have any valid references.

If the first automation is deleted, then you must manually add the references to all of the other automations.

Otherwise, you would typically see these kinds of error messages:

  • Error accessing Type:
  • Error deserializing Design Component -

Here are examples of the errors you could encounter if the references are missing:

Missing refererences error message

Missing refererences error message

Suggest Edit

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.