Hi Claushingebjerg

Do not use @inherits UmbracoViewPage

You have to write some logic for getting needed properties.

If aliases of properties are the same between all docTypes, you can use "Document Type Compositions", move all properties to composition and then ModelsBuilder will create an interface for you, with your properties:

@inherits Umbraco.Web.Mvc.UmbracoViewPage

Hope it will make sense for you.

Thanks,

Alex

Hi Alex. Not really :), and it throws an error in the partial if i change @inherits UmbracoViewPage<ContentModels.Home> to @inherits Umbraco.Web.Mvc.UmbracoViewPage

 'Umbraco.Core.Models.IPublishedContent' does not contain a definition for 'Opacity' and no extension method 'Opacity' accepting a first argument of type 'Umbraco.Core.Models.IPublishedContent' could be found 

"Opacity" is a doc type parameter on a doctype composition.

And what is the name of your composition?

Can you share the code of all partial?

It should be:

@inherits Umbraco.Web.Mvc.UmbracoViewPage<ICompositionName>

Sure. I've changed it as i understand you. The composition is called "Sidetop"

@inherits Umbraco.Web.Mvc.UmbracoViewPage<Sidetop>
@using ContentModels = Umbraco.Web.PublishedContentModels;


    <section class="imagebg height-50"  data-overlay="@Model.Opacity">
        <div class="background-image-holder background--bottom">
            <img alt="image" src="@Umbraco.Media(@Model.Topbillede).Url" />
        </div>
        <div class="container pos-vertical-center">
            <div class="row">
                <div class="col-sm-12 text-center">
                    <h1>@Model.Overskrift</h1>
            <p class="lead">@Model.Manchet</p>
                </div>
            </div>
        </div>
    </section>

Now throws the following error

Cannot bind source content type Umbraco.Web.PublishedContentModels.Kunstnere to model type Umbraco.Web.PublishedContentModels.Sidetop.

Yup, that did the trick

@inherits Umbraco.Web.Mvc.UmbracoViewPage<ISidetop>
@using ContentModels = Umbraco.Web.PublishedContentModels;

Do you have any documentation on how and why it should be like this or do .net devs just know this "magic"?

Look please this article - http://24days.in/umbraco-cms/2016/getting-started-with-modelsbuilder/

The models builder respects the content type's inheritance, and content type's compositions are represented by interfaces.

To see how the models are generated then you can go into ~/AppData/Models/models.generated.cs and /AppData/Models/all.generated.cs

Final question :)

How do i handle it, if i need to use the same template with 2 different doc types?

I see these ways:

1. GetPropertyValue method and do not use Strongly typed models at all

2. Composition with all used properties or parent document type

3. A lot of if statements with checking is there this property now or no - in other words, make templates general for document types

Hope it makes sense for you.

Thanks,

Alex

In this case number 2 or 3 makes sense as the only difference between the two doc types are internally used fields from a composition.

The doctype aliases are "Kunstner" and "importeretKunstner"

@inherits UmbracoViewPage<ContentModels.Kunstner>
@using ContentModels = Umbraco.Web.PublishedContentModels;

Only handles the "Kunstner" Doctype...

@inherits UmbracoViewPage<ContentModels.Kunstner>
@inherits UmbracoViewPage<ContentModels.ImporteretKunstner>
@using ContentModels = Umbraco.Web.PublishedContentModels;

Seems to work, but is it the right way to do it?

Hi Claushingebjerg

As I know there is no sense to use 2 @inherits It uses only first one

This is the right way to handle compositions:

@inherits Umbraco.Web.Mvc.UmbracoViewPage<ISidetop>

Hope it make sense

Alex

is working on a reply...