Previously, if a type converter was applied to a property of e.g. type string or object then that type converter would never be invoked because the value to be assigned is already of string/object. This is not System.Xaml's behavior as shown by the TypeConverterIsUsedEvenIfMatchingType.
However, fixing this behavior made the ComplexPositionalParameterWrapper fail because an exception is no longer thrown. I can't work out why the exception should be thrown here - the ComplexPositionalParameterWrapper.xml file looks like correct XAML.
Previously, if a type converter was applied to a property of e.g. type
stringorobjectthen that type converter would never be invoked because the value to be assigned is already ofstring/object. This is not System.Xaml's behavior as shown by theTypeConverterIsUsedEvenIfMatchingType.However, fixing this behavior made the
ComplexPositionalParameterWrapperfail because an exception is no longer thrown. I can't work out why the exception should be thrown here - theComplexPositionalParameterWrapper.xmlfile looks like correct XAML.@cwensley any idea what's going on here?