Question

I want to create one View for different Models that are all inherit from the same BaseModel.
But I don´t know which is the right approach.

Why i don´t want to use different/strongly typed views? Because lets say I will build a lampshop and the basemodel defines a lamp. So all models that inherit the basemodel are lamps with the same baseproperties and 1,2,3 special properties. I think it´s not neccessary to build 30-40 Views for almost the same Models.

Answer 1

As you said all lamps are the same except few additional properties. Imagine that properties as extensions to base class. Base class allows existance of extensions(through LampSpecialProperties), but does not care about their content. Then you could define models like this

public class LampViewModel
{
   public string SomeProperty {get;set}
   public LampSpecialProperties SpecialProperties {get;set;}
}

public abstract class LampSpecialProperties
{ }

public class SomeConcreteLampSpecialProperties : LampSpecialProperties
{
     public string BrightnessLevel {get;set;}
}

In your view, display the lamp base model properties and then the extension properties

@model LampViewModel
... some shared properties    
@Html.DisplayFor(model => model.SpecialProperties)

In Views/DisplayTemplates you could have templates for every concrete implementation of those LampSpecialProperties

@model SomeConcreteLampSpecialProperties
@Html.DisplayFor(model => model.BrightnessLevel)

For another lamp

@model SomeAnotherConcreteLampSpecialProperties
@Html.DisplayFor(model => model.FuelConsumption)// sounds scarry :)

And so forth for all the lamp extensions.

But this all is about your domain and business logic. If your business requires 30-40 model classes anyways, you should create them one by one