Hi folks,
I've gone through a number of iterations with this problem and can't seem to find an agreeable solution.

I have a really simply basic class I'm using in a lot of different places with the content being altered by the UmbracoPropertiesAttribute with prefix.

My interface

public interface IBasicContentViewModel {
    public string Title { get; set; }
    public HtmlString Content { get; set; }        
    public bool HasContent { get; }
}

My basic implementation

public class BasicContentViewModel : IBasicContentViewModel {
    [UmbracoProperty(AltPropertyAlias = "Name")]
    public string Title { get; set; }

    [UmbracoProperty]
    public HtmlString Content { get; set; }        

    [DittoIgnore]
    public bool HasContent { get { return Content != null && string.IsNullOrWhiteSpace(Content.ToString()) == false; } }
}

This is then inherited by specific use viewmodel.

[UmbracoProperties(Prefix = "signUpComplete_")]
public class SignUpCompleteContentViewModel : BasicContentViewModel {
}

Or...

[UmbracoProperties(Prefix = "signUpForm_")]
public class SignUpFormContentViewModel : BasicContentViewModel {
}

The content all belongs to the same page separated by tabs (hence the prefix) then an Controller action (Alt Template) will the Dittofy the right view model.

The reason this doesn't work is the property which is getting value resolved by UmbracoPropertyAttribute is on the BasicContentViewModel not the actual class being Dittofied. So when the UmbracoPropertyAttribute looks for a prefix it won't find the UmbracoPropertiesAttribute and therefore won't find the value. I've done some tests with a basic ValueResolver and sure enough the UmbracoPropertiesAttribute is null.

This doesn't seem like a problem that's easy to resolve as doing a watch the Context from that test at no point does the property mention the actual calling type just the type of the class which the property belongs too.

My original solution was to use an interface on every class where I'd want a prefix and then implement the UmbracoPropertyAttributes but that led to a lot of repetition. I basically need a situation where

I'm trying to be as DRY as possible here but it seems I might not be successful.

Thanks,
Jamie