About the MyContent namespace

The MyContent namespace lets you create references in scripts to tie together the content added to a single layout. The layout content can consist of graphics, apps, other layouts, and controls. The MyContent namespace encompasses everything the layout contains, including:

• Public custom properties of graphics associated with the layout

• Exposed properties of apps contained in the layout

• WPF dependency properties of apps contained in the layout

The exposed properties of each app are listed in the AppManifest.xml file for the app.

Note: Event-handler scripts, unlike named and built-in scripts, do not require the use of the MyContent namespace when scripting app or control properties and methods. To script a property or method, start by entering the name of the control instead of "MyContent." The autocomplete function will allow you to see the properties and methods of the control as you type.

Properties designated as private are not accessible in the MyContent namespace. Each layout has its own MyContent namespace and you cannot create references to properties in another layouts via this namespace. If you need to reference properties in a different layout, use the ViewApp namespace and create attributes as needed for the references. See About ViewApp namespaces for more information.

Note: MyContent Namespace properties cannot be referenced from an object script. References from object scripts will validate successfully within the script editor, but a configuration error message will be displayed when you save the object. Objects that contain a script that references a MyContent Namespace property will remain in a warning state and the reference will not resolve.