Hi all,

We're currently working on an MVC 7.5 site, that has some 30 different page types. There are 12 particular properties that are randomly used by some of these page types, and not others. Ordinarily if these properties were used by all of the page types we would add them to a base class and use inheritance - in this scenario that wouldn't work because too many of the derived page types would end up with properties they shouldn't have.

An example of the properties I mention can be seen at: https://www.dropbox.com/s/ds12xr09m1cllgt/capture.png

Therefore, the two choices I foresee are:

1) Add the properties to a base class, and then on the derived types that don't need a particular property, add the [Ignore] and [ScaffoldColumn(false)] attributes. This just feels a little bit of a hack.

2) Break the properties down into individual interfaces, and individually implement them on the page types that need them e.g. IHasTitle, IHasSubtitle etc. The AlloyTech MVC site uses this approach.

I'm not particulary sold on either solution, although I have less issues with the later - it at least provides the additional benefit of being able to query types based on whether they implement a particular interface.

I'd be really interested to hear others thoughts on this. Have you had similar challenges, and if so what route did you take?

Thanks in advance

Al