MC6028: {0}:TypeArguments="{1}" is not valid. '{2}' is not a valid type name reference for the generic argument at position '{3}'.
MC6023: Because '{0}' is implemented in the same assembly, you must set the {1}:Name attribute rather than the Name attribute. ...
MC6024: '{0}' root element requires a {1}:Class attribute to support event handlers in the XAML file. Either remove the event ...
MC6025: '{0}' root element is a generic type and requires a {1}:Class attribute to support the {1}:TypeArguments attribute ...
MC6026: '{0}' root element requires a {1}:Class attribute because '{2}' contains a {1}:Code tag. Either remove {1}:Code and ...
MC6028: {0}:TypeArguments="{1}" is not valid. '{2}' is not a valid type name reference for the generic argument at position ...
MC6031: {0}:FieldModifier attribute cannot be specified because a {0}:Class attribute is also required to generate a Name ...
MDI Applications do not support the SplitContainer. A Splitter control will be added to the Form instead of a SplitContainer. ...
MDI Applications do not support the SplitContainer. A Splitter control will be added to the Form instead of a SplitContainer. ...
Media link object of type '{0}' is configured to use the MIME type specified in the property '{1}'. However, that property's ...