Removing the optional "Extension" suffix from Markup Extension name if present.
Made it possible to add resources to a ResourceDictionary through DesignItemProperty.CollectionElements.
Fixed bug; Only sets the inner text of an XML element if the element type defines a Content property.
Its WPF standard to use parent type name as prefix before the dot when declaring a property as XAML element, and NOT the name of the type that declares the property.
Fixed so Resources are always first among child items.
Added generated GlobalAssemblyInfo.cs to avoid the requirement to compile whole SharpDevelop solution before loose referenced projects can compile.
Merge remote-tracking branch 'upstream/master'
XML-namespaces for controls outside the default XML-namespace is now declared in the document root.
As prefix for the XML-namespaces it primarily uses the value from XmlnsPrefixAttribute if it exists for the XML-namespace, otherwise a "ControlsX" name is generated, where X is the first free value.
Fixed so nodes in the property grid gets DesignItemProperty instances that really represents attached properties when an attached property is used.
When setting a property value as attribute, fixed so namespace prefix is only used for attached properties, and if no prefix is defined for a non-default namespace a new unique prefix is generated.
Removed Ignore attribute from SimpleLoadTests so the tests in the class will be executed.
Made some modifications to XamlParser so it aligns with the official XamlReader and the SimpleLoadTests will pass.
Removed Ignore attribute from WhitespaceTests so the tests in the class will be executed.
Made some modifications to XamlParser so it aligns with the official XamlReader and the WhitespaceTests will pass.
If the ParentProperty is a collection the collection itself is the TargetObject (for example when adding Bindings to the MultiBinding.Bindings property).
Fixed bug where list with errors in the designer was only updated if the document failed to load completely.
The previous solution regarding XAML names expected all properties of type string named Name to represent a name in XAML namescope, and this caused trouble with types with a property named Name that did not represent a XAML name. In this case the value of the property tried to be registered as name to the namescope and this caused either the value to be occupied as name, or threw an exception if name already was taken or the value consisted of characters forbidden in XAML names causing the value to not be set at all.

To solve this the value of a Name property is only registered to namescope if the property represents a XAML name (defined by RuntimeNamePropertyAttribute).

Also added a Name property to XamlObject that always sets the name to x:Name attribute, but gets it from either x:Name or the property that represents the XAML name if it exists (both are valid places for name registration).

Fixed a bug in XamlParser where x:Name value was not registered in its namescope.

All other changes (for example changes in PropertyGrid/XamlDesignItem) was to support the Name fixes described above.
Throws a XamlLoadException with an error message describing the error instead of a NullReferenceException in the case where the document failed to load.
Sending in an empty string as namespaceURI when setting a value to an attribute that does not belong to a namespace, otherwise it will overwrite the value in another attribute with same name but in another namespace if it finds one.
Fixed missing namespace prefix on properties that is set as elements on types outside default XAML namespace.
Fixing this in CreatePropertyElement method also fixed another bug for AddChildNodeToProperty method that was fixed earlier in InsertNodeInCollection method with commit comment as follows:
"Its WPF standard to use parent type name as prefix before the dot when declaring a property as XAML element, and NOT the name of the type that declares the property."
Revert "Added generated GlobalAssemblyInfo.cs to avoid the requirement to compile whole SharpDevelop solution before loose referenced projects can compile."

This reverts commit ad869adade1a989cd24ee58497a625dd28a640cf.
Added default ReportErrors delegate that does nothing.

This is necessary after the fix in commit 295f62532f3be6cb42ed15128806afe08ca67a10.
Before that commit the ReportErrors was semi-optional; When loading was successful ReportErrors was never called (ReportErrors optional), but when document failed to be created a NullReferenceException was thrown because ReportErrors did not have a delegate.

See also commit 006558f253769244bfd0141b75d8ce1a6c52b62c, that throws a more friendly exception than NullReferenceException when document fails to load.
Fixed so its possible to use MultiBinding and PriorityBinding on a DesignItemProperty and that it writes as expected to XAML.