I have listed this as a breaking change because:

• This requires that the overloads to the GetPropertyValue methods of the PublishedContentExtenions class return an 'object' not a 'string'. This is required in order to get the IPropertyEditorValueConverters to work because they can return any object. If we keep the 'string' returned then there is no point in the value converters as it will always be string. The only other option is to create new extension methods which contain the value conversion but this seems silly and redundant. For the most part, people wont even recognize this change since in their views any 'object' gets rendered to it's string equivalent. The only people who might see breaking changes is when doing things like Linq statements. For example, this used to work:

var result = doc.Ancestors().OrderBy(x => x.Level)
    .Single()
    .Descendants()
    .FirstOrDefault(x => x.GetPropertyValue("selectedNodes", "").Split(',').Contains("1173"));

but now that won't compile because GetPropertyValue returns 'object' not string, so you'll have to either cast it to a string or use the strongly typed method:

var result = doc.Ancestors().OrderBy(x => x.Level)
    .Single()
    .Descendants()
    .FirstOrDefault(x => x.GetPropertyValue<string>("selectedNodes", "").Split(',').Contains("1173"));

<Comment was deleted>

Didn't know this was already implemented in 4.11. It works great! Here is an example which can be used with the DAMP Property Editor Value Converter package:

var brandboxImages = brandboxItem.GetPropertyValue<DAMP.PropertyEditorValueConverter.Model>("brandboxImageDamp");
        
<div class="slide">
            
    @foreach(var media in brandboxImages)
    {
        <img src="/img/spacer.gif">