MVC Controls Toolkit is a complete set of advanced server controls for
MVC 2-5 ranging from a templated edit-on line datagrid to date-picker and custom formatted textboxes, supporting client validation and
globalization. MVC Controls Toolkit makes it easier to define new complex controls for MVC without defining custom binders to read back the input from the Controls because each
control enables the MVC engine to call its own handler to bind properly the input to the view model. Thus, there is no need to adapt the controller to a
control or to define ad hoc controllers.
Commercial Version: Data Moving Controls Suite
We reached big results and the Mvc Controls Toolkit is at the moment the more famous complete free controls suite available for Asp.net Mvc. We are the first ones on Google under
the keyword: Mvc Controls. If the Mvc Controls Toolkit was useful to you
boost your development buying its commercial version:
The Data Moving Plug-in controls suite contains
several more controls, and features that enable you to implement advanced and futuristic Views in a few minutes.
Commercial Version Demo Videos
NEW TO THE MVC CONTROLS TOOLKIT?
- See the list of all Mvc Controls Toolkit Tutorials
- Download complete examples here
- See the installation procedure
here. Avaliable also NuGet packages:
- See full documentation
- See Releases History here.
- Read about the theory that is behind the Mvc Controls Toolkit
FEEL FREE TO CONTACT US
Mvc Controls Toolkit Features
- All controls and validation attributes support culture
globalization of dates and numbers, and support both server-side and client-side validation (see
Validation Settings section).
- Compatible with both Mvc 2, Mvc 3, Mvc4;
- Client side ViewModell automatically synchronzed with the server ViewModel that can be bound to UI elements. See here.
- Client-Side Templates for creating rich UI at a low BandWidth price,
- Support for Theming. See here.
- Items Controls
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
- Data Annotations and Validation Attributes with full support for client side validation and globalization
- Action Filters and View Results
- Controls code appears only in the Views not in the Controllers, thus keeping separation of concerns between View (How to display) and controller (What to display)
- When possible multi-parts controls are not rendered as a single piece, but the View designer has the freedom to display its parts separately whererever he prefers. Moreover, the View designer has the possibility to render only the parts it needs,
if this makes sense.
- Defining new controls with the same features of the pre-defined controls is straightforward, see here.