Building forms is really easy! Bind a collection of objects in the ComboBox control and let the user select the value.

DotVVM syntax is different from Razor. The Validator control can display validation errors for a particular property. You can choose to apply CSS classes on any element based on validation state of some property.

DotVVM syntax is different from Razor. Instead of passing lambda expressions, use _root, _parent or _this expressions to reference different scopes in your viewmodel.

DotVVM syntax is different from Razor. Instead of concatenating fragments of CSS classes, just use class-* property and specify a boolean expression indicating whether the class shall be included or not.

DotVVM syntax is different from Razor. Instead of concatenating parts of URLs, the RouteLink component can build links to other pages from the route name and its parameters.

DotVVM syntax is different from Razor. Instead of foreach blocks, use the Repeater control and bind it to a collection of objects.

DotVVM syntax is different from Razor. Instead of the @if statement, use the Visible property on any HTML element and bind it to a boolean expression.

In the previous part, you could learn about the new approach for creating custom controls in DotVVM – the Composite controls. I’ve shown how to declare a composite control, how the new type ValueOrBinding<T> works, and how to work with templated controls.

DotVVM 4.0 has introduced a new way of building custom controls called Composite controls. In this article, we’ll share multiple use cases for these controls, and also some useful tips and tricks how to use this concept efficiently.

We are happy to announce the release of DotVVM 4.0. This version contains several new features, many bug fixes and some significant performance improvements.