Throwing a DotvvmControlException requires an instanceīy default, the GetContents method should be static and can return either a collection of controls, or a single DotvvmControl instance.

Keep in mind, that composite controls cannot contain ContentPlaceHolder controls, as the content for the master pages are resolved before the Load phase when the composite controls call their GetContents method.įor this reason, layout-like controls such as Container in Bootstrap 5 were written in an old-fashioned way. SetAttribute('title', toolTip) if (overlay is not null)Ĭomposite Controls Cannot Contain ContentPlaceHolder Yield return new HtmlGenericControl('img', htmlCapability) = DotvvmProperty.Register(c => c.Style, CardImageStyle.Default) public IEnumerable GetContents( AddCssClass($'badge public static readonly DotvvmProperty StyleProperty Return new HtmlGenericControl('span', textOrContentCapability, htmlCapability) ValueOrBinding type,īadgeVisualStyle visualStyle = BadgeVisualStyle.Default, TextOrContentCapability textOrContentCapability, By using this approach, the control code appears much more attractive and readable.įor instance, consider the following example of a Bootstrap Badge control: public class Badge : BootstrapCompositeControl

Instead, it only requires declaring a ` GetContents` method and placing individual control properties as arguments of the method. This approach eliminates the need to declare DotVVM properties in code-only controls, for which you had to use the dotprop code snippet and work with long property declaration blocks.

You may already be aware that DotVVM 4.0 has introduced a new feature called Composite Controls, which provides a new way to write controls in DotVVM.

Vmware extension pack