MVCControlsToolkit Wiki Rss Feed

Updated Wiki: Pager

frankabbruzzese — Sat, 18 May 2013 21:17:37 GMT

Pager

This control needs reference to both MVCControlToolkit.Controls-x.x.x.js or the smaller MVCControlToolkit.Controls.Core-x.x.x.js, jquery-1.4.2.js(or better).js.

There are three pager helpers:

Submit Pager that performs a submit (Ajax or normal) in the form it is in and it is better suited for data editing purposes,
Get Pager that performs a simple get (Ajax or normal) to a completely configurable route, and it is better suited for REST displaying of data.
Client Pager All its buttons are not rendered by the server, but they are created and modified dynamically on the client side each time the page changes. It triggers a javascript event when the page changes, but it can optionally cause a form submit. Since it doesn't need the server to render its buttons it is well suited for paging data to be retrieved through ajax calls that returns json data, or for paging local javascript data.

Mvc Controls Toolkit pagers, essentially handle adequately an integer property of the View Model containing the current page of some data that are currently displayed.

Its buttons and page links have the only effect of modifying this property, and performing a either submit or a get to a configurable Route(according to which overload is used). Then, it is up to the Controller to handle properly the actual data.

There are buttons for the first, netx, previous, and last page and a component containing directly the page links. For the last one the user can choose how many page links to show. Links and buttons appear enabled or disabled adequately. If the user supplies also a Total Count of the pages it will be used properly in enabling/disabling buttons and links, however it is not obligatory.

Each component can be rendered separately and one can decide if using it or not. Thus, you can decide to use just next or previous page buttons or just the page links, or a mix of the two....Whatever you want!

Each button can be displayed either as a normal button or as a link or as an image link. Select the one you prefer by using the PageButtonStyle enumeration.

If you supply also a Previous Page field the Pager will just mantain its value when the View is posted. It is useful on the server side to know on what page possible modifications(deletion, modification or insert) were done. However this parameter is not compulsory.

Submit Pager

Below an example of use of the submit causing pager helper:

                    <% var pager = Html.PagerFor(m => m.Page, m => m.PrevPage, m => m.TotalPages); %>
                    
                    <%:pager.PageButton("<<", PageButtonType.First, PageButtonStyle.Link) %>
                    <%:pager.PageButton("<", PageButtonType.Previous, PageButtonStyle.Link) %>
                    <%:pager.PageChoice(4, pageNames: p => string.Format("({0})", p)) %>
                    <%:pager.PageButton(">", PageButtonType.Next, PageButtonStyle.Link) %>
                    <%:pager.PageButton(">>", PageButtonType.Last, PageButtonStyle.Link) %>
                    
                    <%:pager.PageButton("Go To", PageButtonType.GoTo, PageButtonStyle.Button) %><%:pager.GoToText(new {style="width:50px;" })%>

It is applied to the same example of the DataGrid that is here. You can find both examples in the binary distribution. For a complete example application see here.

Please notice the pageNames: parameter that allows the user to provide a function that transfrorms page numbers into strings. In the example above it is used just to put '()' around the page numbers, but it can be used also to implement a dictionary type of paging. That is, a paging based on the first characters of a string that someway represents the record(for instance all customers whose surname starts with 'A'). Disabled buttons are applied the attribute disabled="disabled" as usual for disabled elements. The current page is applied the attribute: selected-page="selected". Both can be used to create CSS rules for styling the involved nodes. Please notice that all browsers, already apply some standard styling to all disable input fields, while internet explorer apply such a style, not only to input fileds and buttons, but also to all other disabled DOM nodes, such as images, and links.

Get Pager

The get causing helper works in a similar way. Only the first of the above instruction change:

 public static Pager<VM> Pager<VM>(
           this HtmlHelper<VM> htmlHelper, int currPage,
           string parameterName, 
           string actionName,
           int? totPages = null,
           string targetIdName = "",
           string controllerName = null,
           object otherParameters = null,
           string routeName = null,
           string protocol = null,
           string hostname = null,
           string fragment = null)

Where:

currPage is the current page
parameterName is the Route parameter name where to put the page number of the various links
totPages, is the opttional count of the total pages
targetIdName is the id of an html element to use as atrget for an ajax call. If it is provided the pager will do an ajax call instead of a normal get
otherParameters is an anonymous object containing all other parameters for the Route.
All other parameters define the Route as in an Action Link.

Client Pager

There are two overload of the client pager:

        public static ClientPager<VM>  ClientPagerFor<VM>(
           this HtmlHelper<VM> htmlHelper,
           Expression<Func<VM, int>> page,
           Expression<Func<VM, int>> totPages=null,
           string pagePrefix=null, string pagePostfix=null,
           bool causeSubmit=false)

Where:

page is an expression locating the page property within the ViewModel
totPages is an optional expression locating a property containing the total pages within the ViewModel
pagePrefix and pagePostfix are optional strings that are prefixed and postfixed to the page number
causeSubmit when true causes the submit of the form that contains the pager when a page change occurs. It is useful mainly to trigger ajax calls tht return json data, instead of returning html.

If the pager is rendered within a Client Block both the page and total pages properties of the Client Side ViewModel are bound to the pager with adequate knockout bindings . This way each time they change the appearence of the pager changes immediately to reflect the new values.

In case we don't use knockout and/or Client Blocks we can update the pager with new data with the function:

MvcControlsToolkit_NewPage(pagerId, newPage, newTotalPages)

pagerId can be computed with the PrefixedId helper by writing something like: @Html.Prefixed(m => m.ModelPageField)

Each time the page changes the pager triggers an event:

trigger("queryChanged", data);

where the data object contains the following fields:

type, specifies the kind of query information that changed. For the pager its value is the string: 'page'.
submit, by setting this value to true within our event handler we can cause a form submit. By setting it to false we prevent a form submit. The value passed initially in this field is the causeSubmit of the pager helper.
page, the current page.
previousPage: the previous page.
totalPages, the total pages, if available.

The event bubbles through the ancestors chain, so we can specify an event handler in any DOM ancestor of the pager.

The second overload of the pager doesn't use expressions, but fileds names and values (as for TextBox instead of TextBoxFor) :

public static ClientPager<VM> ClientPager<VM> (
           this HtmlHelper<VM> htmlHelper,
           string pagerName,
           int initialPage=1,
           string totalPagesName=null,
           int ? totalPages=null,
           string pagePrefix = null,
           string pagePostfix = null,
           bool causeSubmit=false)

where:

pagerName, is the name of the property containing the current page
initialPage is the page initially displayed by the pager
totalPagesName is the name of the property containing the total pages
totalPages is the initial value of the total pages.
all other parameters are the same as the ones of the other overload

New Comment on "TypedTextBox"

frankabbruzzese — Fri, 17 May 2013 06:44:41 GMT

No textareas are not supported. The main purpose of the TypedTextBox is formatting, and keyboard handling for dates and numbers. Textareas are just for strings, so you have no formatting problem. You may simply use a jquery watermark plugin

Updated Wiki: Home

frankabbruzzese — Sun, 05 May 2013 19:00:30 GMT

Project Description
MVC Controls Toolkit is a complete set of advanced server controls for MVC 2-4 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.

Main object of the project

Enabling MVC programmers to implements rich user interfaces without renouncing to the separation of concerns between the View Model that defines just What data to display and the View that defines How to display those data: in particular in no case the choice on how to display data in a View must force the programmer to change the View Model.

HELP US WITH A DONATION!
The Mvc Controls Toolkit project is not sponsored by any big company and relies on donations to continue. 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. However we cannot survive without donations.

2013-05-02. The Data Moving RTM has been closed! We are preparing the documentation, and a commercial Web Site. The RTM will be ready for purchase ASAP.

2013-04-25. Give a look to the Data Moving Plug-in Amazing Features and to the Data Moving Plug-In on Actual Mobile Devices

2013-04-20. Attention the current release is compatible with jquery 1.9.1, however you must use the more recent version of the following files: jquery.unobtrusive-ajax(last), jquery.validate.unobtrusive (last), jquery.validate-1.11.1, and knockout-2.2.1(new knockout package available in the download area).

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Data Annotations

frankabbruzzese — Sun, 05 May 2013 10:21:02 GMT

Data Annotations

Data annotations are defined in the namespace MvcControlsToolkit.DataAnnotations.

CanSortAttribute . It can decorate properties of a View Model. It declares that a property can be used for user specified sorting and filtering. The EnableSortingFor and DataFilterClauseFor helpers just cancel sorting and filtering requirements on properties that are not decorated with the CanSortAttribute. The CanSortAttribute has two properties Allow and Deny. Only filtering operations listed in Allow but not listed in Deny will be accepted. Both Allow and Deny accept the bitwise or of items from the enumeration: MVCControlsToolkit.Linq.FilterCondition. Their default values are:

            Allow = FilterCondition.Equal |
                FilterCondition.LessThan |
                FilterCondition.LessThanOrEqual |
                FilterCondition.GreaterThan |
                FilterCondition.GreaterThanOrEqual |
                FilterCondition.NotEqual |
                FilterCondition.StartsWith |
                FilterCondition.EndsWith |
                FilterCondition.IsContainedIn |
                FilterCondition.Contains;
            Deny = FilterCondition.IsContainedIn |
                FilterCondition.Contains;

The methods:

public static FilterCondition AllowedForProperty(Type type, string propertyName)

public static FilterCondition AllowedForProperty<T, F>(Expression<Func<T, F>> field)

rerturn the operations allowed on a given property of a given class.

While the methods:

public static FilterCondition AllowedForProperty(FilterCondition conditions, Type type, string propertyName)

public static FilterCondition AllowedForProperty<T, F>(FilterCondition conditions, Expression<Func<T, F>> field)

intersects a set of given operations with the set of allowed operations.

FormatAttribute . It inherits from the DisplayFormat .Net attribute, and has mainly its same functions. The only difference being that it has three more string properties: Prefix, Postfix, and ClientFormat. The ClientFormat string specifies a formatting rules to be applied on the client. The sintax of the client formatting rules is defined here: https://github.com/jquery/globalize. In addition to the standard formats listed there we added also the "G" date format, since it is the default date format used in .Net. The others two strings are then chained before and after the result of the previous step. If the values are rendered with the TypedTextBox or TypedTextBoxFor helper, when the user edit the field both Prefix and Postfix strings disappear and the ClientFormat appears in a simplified version, and everything reappear as before at the end of the editing. In case the input field is empty they are absent too, and a WaterMark is displayed. The Prefix, Postfix, and ClientFormat are available in the MetaData AdditionalValues property with the names: MVCControlsToolkit.ClientFormatString, MVCControlsToolkit.ClientFormatPrefix, MVCControlsToolkit.ClientFormatPostfix. If the above properties are not defined and the ExtractClientFormat is set to true they will be extracted automatically from the server side format string. Prefix and Postfix can be also stored in a resource file to allow their localization by using the constructor: public FormatAttribute(Type resourceType, string prefixKey, string postfixKey). When the ClientFormat property has not been provided, if the property ExtractClientFormat is true the client format is extracted from the DateFormat property inherited from the DisplayFormat attribute. This might cause javascript errors if the server side format is not supported by the client side globalization library.

MileStoneAttribute. It can decorate properties of a View Model and has no properties and no parameters. It just declares that the property must not be displayed in edit mode but that it should be used to give hints or constraints to a user input. DynamicMinimum and DynamicMaximum such as the ones used with the DateRangeAttribute might be decorated with this attribute if one don't want the user be able to change them on the client side. When input controls capable of enforcing DynamicMaximum and DynamicMinimum immediately on the client side see this attribute they decide a fixed value for this constraints once and for all on the server side when the control is rendered, and then use them on the client side. On the contrary, if no such attribute is found the control expects the DynamicMaximum and DynamicMinimum be available on the client side in some input field and that they might be changed by the user. If the values are not rendered with controls capable of enforcing automatically DynamicMinimum and DynamicMaximum on the client side the MileStone attribute gives to the View designer, the hint to display adequate messages to drive the user.

DateRangeAttribute. One can apply more than a DataRange attribute to each DateTime property. Each of them can specify both static Minimum and Maximum(called SMaximum and SMinimum) and dynamic Minimum and Maximum(called DynamicMinimum and DynamicMaximum).

SMaximum and SMinimum may set either to a string representing a date in international format, or to a date spefified through an offset relative to "Now" or "Today", The syntax of th string is as follows:

SMinimum="Now-1h+3d..." or SMinimum="Today+1h-3d..."

where:

s: seconds
m: minutes
h: hours
d:days
M: moths
y: years
T: it comes without any number before. It takes a value from HttpContext.Current.Items["CurrentTimeShift"] and add or subtract it. The value here must me an integer that is interpreted as a number of hours. The developer can use it to handle timeline difference between client and server. The value in HttpContext.Current.Items["CurrentTimeShift"] can be taken from the user preferences or a cookie or autodetected from the browser (at least one post is needed to perform autodetect).
t: tolerance on the server. Tolerance in minutes, that is used to validate the constraints on the server. It is needed to take into account difference between the server and client clocks, but Mainly the time delay due to the computation+user processing time. Without this tolerance a date might be validated succesfully on the client but might fail on the server.

For a concrete example of use of the SMinimum and SMaximum see this tutorial where they are used together with a DataGrid.

The property C to be used as either dynamic maximum or as dynamic Minimum for a property X is defined with a string containing the dot separated list of properties to reach C from the father object of X(the object where the property X is defined).

The value of C will be used both to do server side validation and to force the possible choices of the DropDowns of X on the client side. If C is rendered in the View as an input field, the values inserted by the user for C will be used to constrain the possible input for X directly on the client side.

Delays can be applied to both dynamic minima and dynamic maxima in the DateRange attribute. For instance, one can requires X be 5 days before C. What Happens on client side when a constraint is violated depends on the value of the RangeType property of the DateRange attribute:

X has RangeType set to Verify and C is not rendered as an input field and it is decorated with the MileStone attribute. The value of X is forced to conform with the constraint imposed by C.
X has RangeType set to Verify and C is rendered as an input field and
it is not decorated with the MileStone attribute. The value of X is forced to conform to the constraint imposed by the value of C. When the user changes the value of C, the change is immediately reflected both on the value of X and on the possible choices in the DropDowns of X, specifically: the value of X will be possibly changed to satisfy the constraint imposed by C, and the DropDownsof X will only allow values compatible with such a constraint.
X has RangeType set to Propagate and C is rendered as an input field and has a simmetric DateRange attribute with a TargetType set to Propagate . When the user changes the value of one of them the value of the other changes atuomatically to conform with the constraint. For instance, suppose you have an activity whose minimum duration is one week. By using a RangeType of Propagate for both the start and the end date of the activity and a delay of one week, the user can change both dates freely but when it do a change to one of them the other date is changed to enforce the one week minimum duration constraint.

The MileStone attribute declares that a property has been inserted in the Vie Model just to drive the user to insert an input confroming with some constraints, and that its value will not be rendered as an input fileld.

Delays can be specified either as static TimeSpans or dynamically, however in any case changes in their values on the client side are not supported(it makes no sense to allow the user to change the delay).

It is worth to point out that each property may have several DateRange attributes. Thus, complex network of constraints can be handled on the client side(be careful to avoid circular dependencies and inconsistent constraints).

Caution need to be taken when verifying dynamic constraints on the server side, because the sensible data defining the constraint (that maybe either a dynamic delay or a dynamic minimum or maximum) cannot be taken from the model extracted by the data posted back by the user. Data coming from the client side are always to be considered unreliable because of both malicious users or simple errors. Therefore validation need to be performed or repeated after having retrived these sensible data from a data store.

For a concrete example of use of the DynamicMinimum and DynamicMaximum see this tutorial where they are used together with a DataGrid.

DynamicRangeAttribute . On the server side acts exactly in the same way as the DateRangeAttribute (see above) but with numeric types. On the client side constraints are not propagated automatically as in the case of the DateRangeAttribute but use the standard client validation mechanism based on error signalling.

RequiredFieldsAttribute . Object level validation attribute that controls all required fields of an object. The required fields are listed in the Fields property of the attribute as a comma separated list of field names. Fields to be cotrolled can be specified also in object contained as properties of the root object, for instance PersonalInfos.Name stands for the Name property of the object contained in the PersonalInfos properties of the root object. Being a class level attribute it can be applied directly on an entity class, thus allowing the use of a single metaclass for both the business(or entity ) class and all related ViewModels, since all other property level constraints applies wherever the involved property is used. Since it is not intended for being automatically controlled by the MVC engine it can be verified with the help of the static methods of the Validator class. If the RejectEmptyIEnumerables parameter of the attribute is set to true, the attribute triggers also when a property is an empty collection.

Updated Wiki: Data Annotations

frankabbruzzese — Sun, 05 May 2013 10:10:37 GMT

Data Annotations

Data annotations are defined in the namespace MvcControlsToolkit.DataAnnotations.

            Allow = FilterCondition.Equal |
                FilterCondition.LessThan |
                FilterCondition.LessThanOrEqual |
                FilterCondition.GreaterThan |
                FilterCondition.GreaterThanOrEqual |
                FilterCondition.NotEqual |
                FilterCondition.StartsWith |
                FilterCondition.EndsWith |
                FilterCondition.IsContainedIn |
                FilterCondition.Contains;
            Deny = FilterCondition.IsContainedIn |
                FilterCondition.Contains;

The methods:

public static FilterCondition AllowedForProperty(Type type, string propertyName)

public static FilterCondition AllowedForProperty<T, F>(Expression<Func<T, F>> field)

rerturn the operations allowed on a given property of a given class.

While the methods:

public static FilterCondition AllowedForProperty(FilterCondition conditions, Type type, string propertyName)

public static FilterCondition AllowedForProperty<T, F>(FilterCondition conditions, Expression<Func<T, F>> field)

intersects a set of given operations with the set of allowed operations.

SMinimum="Now-1h+3d..." or SMinimum="Today+1h-3d..."

where:

s: seconds
m: minutes
h: hours
d:days
M: moths
y: years
T: it comes without any number before. It takes a value from HttpContext.Current.Items["CurrentTimeShift"] and add or subtract it. The value here must me an integer that is interpreted as a number of hours. The developer can use it to handle timeline difference between client and server. The value in HttpContext.Current.Items["CurrentTimeShift"] can be taken from the user preferences or a cookie or autodetected from the browser (at least one post is needed to perform autodetect).
t: tolerance on the server. Tolerance in minutes, that is used to validate the constraints on the server. It is needed to take into account difference between the server and client clocks, but Mainly the time delay due to the computation+user processing time. Without this tolerance a date might be validated succesfully on the client but might fail on the server.

For a concrete example of use of the SMinimum and SMaximum see this tutorial where they are used together with a DataGrid.

X has RangeType set to Verify and C is not rendered as an input field and it is decorated with the MileStone attribute. The value of X is forced to conform with the constraint imposed by C.
X has RangeType set to Verify and C is rendered as an input field and
it is not decorated with the MileStone attribute. The value of X is forced to conform to the constraint imposed by the value of C. When the user changes the value of C, the change is immediately reflected both on the value of X and on the possible choices in the DropDowns of X, specifically: the value of X will be possibly changed to satisfy the constraint imposed by C, and the DropDownsof X will only allow values compatible with such a constraint.
X has RangeType set to Propagate and C is rendered as an input field and has a simmetric DateRange attribute with a TargetType set to Propagate . When the user changes the value of one of them the value of the other changes atuomatically to conform with the constraint. For instance, suppose you have an activity whose minimum duration is one week. By using a RangeType of Propagate for both the start and the end date of the activity and a delay of one week, the user can change both dates freely but when it do a change to one of them the other date is changed to enforce the one week minimum duration constraint.

For a concrete example of use of the DynamicMinimum and DynamicMaximum see this tutorial where they are used together with a DataGrid.

Updated Wiki: Home

frankabbruzzese — Thu, 02 May 2013 17:35:29 GMT

Main object of the project

2013-05-02. The Data Moving RTM has been closed! We are preparing the documentation, and a commercial Web Site. The RTM will be ready for purchase ASAP.

2013-04-25. Give a look to the Data Moving Plug-in Amazing Features and to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Home

frankabbruzzese — Thu, 02 May 2013 17:34:49 GMT

Main object of the project

2013-05-02. The Data Moving RTM has been closed! We are preparing the documentation, and a commercial Web Site. The RTM will be ready for purchase ASAP.

2013-04-25. Give a look to the Data Moving Plug-in Amazing Features and to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Globalization

frankabbruzzese — Mon, 29 Apr 2013 21:26:55 GMT

Globalization

Mvc Controls Toolkit extends the predefined client side validation of MVC to allow globalization of input formats. Moreover, all validation attributes defined in the MVC Controls Toolkit supports globalization.

Globalization support may come either from the Old Ajax Microsoft javascript library or by JQuery globalization library. The toolkit automatically detects which globalization library is used with no need for further settings to be specified.

MVC2 users and in general users that take advantage of Old Microsoft Validation library are required to use Old Microsoft Ajax Globalization library, while users of MVC 3 with JQuery Ajax and validation enabled are required to use JQuery validation library.

Below the headers required to add Microsoft Ajax library globalization, and validation:

    <% AjaxHelper.GlobalizationScriptPath = "http://ajax.microsoft.com/ajax/4.0/1/globalization/"; %>
    <%: Ajax.GlobalizationScript() %>
    <script type='text/javascript' src="../../Scripts/jquery-1.6.1.min.js"></script>
    <script type='text/javascript' src="../../Scripts/MicrosoftAjax.js"></script>
    <script type='text/javascript' src="../../Scripts/MicrosoftMvcAjax.js"></script>
    <script type='text/javascript' src="../../Scripts/MicrosoftMvcValidation.js"></script>
    <script type='text/javascript' src="../../Scripts/MVCControlToolkit.Controls-x.x.x.min.js"></script>

The AjaxHelper.GlobalizationScripthPath must contain the the url of a folder containing all js files with the specific information of all cultures. In the example I used an URL of the Microsoft CDN. If you would like to copy in your web site those files you need to copy them fom that path because I was not able to find them elsewhere.

Below the headers required to add JQuery library Ajax, globalization, and validation, based on the Globalize library:

    <script type='text/javascript' src="../../Scripts/jquery-1.6.1.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery-ui-1.8.9.custom.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery.validate-1.8.1.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery.validate.unobtrusive.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery.unobtrusive-ajax.min.js"></script>
    <script type='text/javascript' src="../../Scripts/globalize.min.js"></script>
    
    <%: Html.GlobalizationScript() %>
    <%: Html.JQueryDatePickerGlobalizationScript() %>
    
    
    <script type='text/javascript' src="../../Scripts/MVCControlToolkit.Controls-2.2.0.min.js"></script>

The above assumes that the cultures folder containing all js files with the culture specific information is located in the "script" folder of the web site.

If the path is different it needs to be passed as value of the optional argument of the Html.GlobalizationScript function, whose exact definition is:

public static MvcHtmlString GlobalizationScript(this HtmlHelper htmlHelper, string globalizationFolder = "~/Scripts/cultures/")

The Html.JQueryDatePickerGlobalizationScrip() is needed just if one uses the jQuery datepicker someway, Pleace notice that the jQuery DatePicker is automatically used by some overlkoads of the TypedTextBox and of the DateTimeInput. The above calls uses the localization files contained in “~/Scripts/cultures/datepicker/". If do you want to copy the in a local folder, please use this different overloads, that allows the specification of the folder path:

public static
MvcHtmlString JQueryDatePickerGlobalizationScript(

    this HtmlHelper htmlHelper,
string cultureName = 
null, 

    string globalizationFolder = 
"~/Scripts/cultures/datepicker/",

    Func<string,
bool> useCountry = 
null,

    Func<string,
bool> isSupported = 
null)

If the culture parameter is set to null the current thread culture is used (this is the adviced usage).

If the optional function useCountry is supplied, it is passed the string representing the current Culture (such as en-US) and it must return true, if we want to use a globalization file that is specific for both language and Country, otherwise a file specific for just the language is used (in the previous example (en). The default is the x => false function that never use the Country information. The reason to use just the language might be that there is no globalization file for the current language-Country pair. A smart implementation of useCountry might be based on an array containing all supported languages and language-Country pair.

Anagously, if the isSupported function return false no globalization script is inserted.

In order to use all the above methods one is required to include the namespace:MVCControlsToolkit.Controls.Validation: If the Mvc Controls Toolkit is installed through Nuget this namespace is included among the default ones, so you don't need to include it in all pages.

The MVCControlsToolkit.Controls.Validation namespace contains also an helper to support a generic globalization script:

public static
MvcHtmlString LocalizableResourceScript(

    this HtmlHelper htmlHelper,


    string sourceFormat ,

    Func<string,
bool> useCountry = 
null,

    Func<string,
bool> isSupported = 
null)

Where sourceFormat is a format string with an unique “hole” {0} where to put either the two letter language code or the 5 letters language-Country code, according to the value returned by useCountry function.

There is also another more complex overload where the format string is returned by a function that receives as input the 5 letters language-Country code of the current culture:

public static
MvcHtmlString LocalizableResourceScript(

    this HtmlHelper htmlHelper,


    Func<string,
string> sourceFormatCreate,

    Func<string,
bool> useCountry = 
null,

    Func<string,
bool> isSupported = 
null)

We continue to support also the jquery.global library. Below the settings for this library.

    <script type='text/javascript' src="../../Scripts/jquery-1.6.1.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery.validate-1.8.1.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery.validate.unobtrusive.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery.unobtrusive-ajax.min.js"></script>
    <script type='text/javascript' src="../../Scripts/jquery.global.js"></script>
    <%: Html.jQueryGlobalizationScript() %>
    <script type='text/javascript' src="../../Scripts/MVCControlToolkit.Controls-x.x.x.min.js"></script>

The above assumes that the globinfo folder containing all js files with the culture specific information is located in the "script" folder of the web site.

If the path is different it needs to be passed as value of the optional argument of the Html.jQueryGlobalizationScript function, whose exact definition is:

public static MvcHtmlString jQueryGlobalizationScript(this HtmlHelper htmlHelper, string globalizationFolder = "~/Scripts/globinfo/")

With one of the above in place, for instance in the master page, the user is able to insert numbers, dates, and currencies according to his culture server settings.

Updated Wiki: Home

frankabbruzzese — Thu, 25 Apr 2013 11:13:33 GMT

Main object of the project

2013-04-25. Give a look to the Data Moving Plug-in Amazing Features and to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Home

frankabbruzzese — Thu, 25 Apr 2013 11:13:11 GMT

Main object of the project

2013-04-25. Give a look to the Data Moving Plug-in Amazing Features and to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Home

frankabbruzzese — Sun, 21 Apr 2013 18:34:31 GMT

Main object of the project

2013-04-17. Give a look to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Home

frankabbruzzese — Sat, 20 Apr 2013 16:17:49 GMT

Main object of the project

2013-04-17. Give a look to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Home

frankabbruzzese — Sat, 20 Apr 2013 16:12:07 GMT

Main object of the project

2013-04-17. Give a look to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.

Updated Wiki: Data Moving Plug-in Videos and Tutorials

frankabbruzzese — Thu, 18 Apr 2013 08:14:04 GMT

Data Moving Plug-in Tutorials and Videos

The Data Moving Plug-in is in its RC stage, and will be released to the market about the end of April 2013.

Here screenshots of the Data Moving Plug-In on Actual Mobile Devices

Below the list of all available preliminary tutorials and videos:

Single Page Applications 1: Manipulating the Client Side Viewmodel. Discover how both the server, with remote commands, and the User, with UI primitives, can manipulate the client side ViewModel.
Single Page Applications 2: Validation Error Handling. Enhancement to the usual Mvc Client and Server Validation logic, usefull in Single Page Applications: errors bubbling, hidden errors handling, error entities filtering, entity level, and overall model validation.
Single Page Applications 3: TreeIterator. Discover how to change completely the layout of the virtual pages of your Single Page Application, by simply changing the client side ViewModel.
Data Moving Plugin Forms: Detail Views, Data Filtering UI, and Undo/Redo Stack. Data Moving Forms provide standard detail and filter views, but can be customized with any Html. Moreover, all actions performed in edit mode can be undone and re-done with the typical editors undo/ redo buttons.
Data Moving Styling. Discover, how Data Moving controls can be styled. Both Jquery UI and JQuery Mobile styling framework are supported. Moreover, the developer has the option to customize the standard Jquery UI, or JQuery Mobile styling, and to define new styling frameworks. Different styling options can be mixed in the same page, and also in the same control.
Data Moving Controls. A Review of all Data Moving out-of-the-box controls.
Introduction to the Data Moving Plugin. Notde-to-Node Data Binding, Data Interactions, and TreeViews.

Updated Wiki: Data Moving Plug-in Videos and Tutorials

frankabbruzzese — Thu, 18 Apr 2013 08:13:50 GMT

Data Moving Plug-in Tutorials and Videos

The Data Moving Plug-in is in its RC stage, and will be released to the market about the end of April 2013.

Here screenshots of the Data Moving Plug-In on Actual Mobile Devices

Below the list of all available preliminary tutorials and videos:

Single Page Applications 1: Manipulating the Client Side Viewmodel. Discover how both the server, with remote commands, and the User, with UI primitives, can manipulate the client side ViewModel.
Single Page Applications 2: Validation Error Handling. Enhancement to the usual Mvc Client and Server Validation logic, usefull in Single Page Applications: errors bubbling, hidden errors handling, error entities filtering, entity level, and overall model validation.
Single Page Applications 3: TreeIterator. Discover how to change completely the layout of the virtual pages of your Single Page Application, by simply changing the client side ViewModel.
Data Moving Plugin Forms: Detail Views, Data Filtering UI, and Undo/Redo Stack. Data Moving Forms provide standard detail and filter views, but can be customized with any Html. Moreover, all actions performed in edit mode can be undone and re-done with the typical editors undo/ redo buttons.
Data Moving Styling. Discover, how Data Moving controls can be styled. Both Jquery UI and JQuery Mobile styling framework are supported. Moreover, the developer has the option to customize the standard Jquery UI, or JQuery Mobile styling, and to define new styling frameworks. Different styling options can be mixed in the same page, and also in the same control.
Data Moving Controls. A Review of all Data Moving out-of-the-box controls.
Introduction to the Data Moving Plugin. Notde-to-Node Data Binding, Data Interactions, and TreeViews.

Updated Wiki: Data Moving Plug-in Videos and Tutorials

frankabbruzzese — Thu, 18 Apr 2013 08:13:41 GMT

Data Moving Plug-in Tutorials and Videos

The Data Moving Plug-in is in its RC stage, and will be released to the market about the end of April 2013.

Here screenshots of the Data Moving Plug-In on Actual Mobile Devices

Below the list of all available preliminary tutorials and videos:

Single Page Applications 1: Manipulating the Client Side Viewmodel. Discover how both the server, with remote commands, and the User, with UI primitives, can manipulate the client side ViewModel.
Single Page Applications 2: Validation Error Handling. Enhancement to the usual Mvc Client and Server Validation logic, usefull in Single Page Applications: errors bubbling, hidden errors handling, error entities filtering, entity level, and overall model validation.
Single Page Applications 3: TreeIterator. Discover how to change completely the layout of the virtual pages of your Single Page Application, by simply changing the client side ViewModel.
Data Moving Plugin Forms: Detail Views, Data Filtering UI, and Undo/Redo Stack. Data Moving Forms provide standard detail and filter views, but can be customized with any Html. Moreover, all actions performed in edit mode can be undone and re-done with the typical editors undo/ redo buttons.
Data Moving Styling. Discover, how Data Moving controls can be styled. Both Jquery UI and JQuery Mobile styling framework are supported. Moreover, the developer has the option to customize the standard Jquery UI, or JQuery Mobile styling, and to define new styling frameworks. Different styling options can be mixed in the same page, and also in the same control.
Data Moving Controls. A Review of all Data Moving out-of-the-box controls.
Introduction to the Data Moving Plugin. Notde-to-Node Data Binding, Data Interactions, and TreeViews.

Updated Wiki: Data Moving Plug-in Videos and Tutorials

frankabbruzzese — Thu, 18 Apr 2013 08:13:23 GMT

Data Moving Plug-in Tutorials and Videos

The Data Moving Plug-in is in its RC stage, and will be released to the market about the end of April 2013.

Here screenshots of the Data Moving Plug-In on Actual Mobile Devices

Below the list of all available preliminary tutorials and videos:

Single Page Applications 1: Manipulating the Client Side Viewmodel. Discover how both the server, with remote commands, and the User, with UI primitives, can manipulate the client side ViewModel.
Single Page Applications 2: Validation Error Handling. Enhancement to the usual Mvc Client and Server Validation logic, usefull in Single Page Applications: errors bubbling, hidden errors handling, error entities filtering, entity level, and overall model validation.
Single Page Applications 3: TreeIterator. Discover how to change completely the layout of the virtual pages of your Single Page Application, by simply changing the client side ViewModel.
Data Moving Plugin Forms: Detail Views, Data Filtering UI, and Undo/Redo Stack. Data Moving Forms provide standard detail and filter views, but can be customized with any Html. Moreover, all actions performed in edit mode can be undone and re-done with the typical editors undo/ redo buttons.
Data Moving Styling. Discover, how Data Moving controls can be styled. Both Jquery UI and JQuery Mobile styling framework are supported. Moreover, the developer has the option to customize the standard Jquery UI, or JQuery Mobile styling, and to define new styling frameworks. Different styling options can be mixed in the same page, and also in the same control.
Data Moving Controls. A Review of all Data Moving out-of-the-box controls.
Introduction to the Data Moving Plugin. Notde-to-Node Data Binding, Data Interactions, and TreeViews.

Updated Wiki: Data Moving Plug-in Videos and Tutorials

frankabbruzzese — Thu, 18 Apr 2013 08:13:03 GMT

Data Moving Plug-in Tutorials and Videos

The Data Moving Plug-in is in its RC stage, and will be released to the market about the end of April 2013.

Here screenshots of the Data Moving Plug-In on Actual Mobile Devices

Below the list of all available preliminary tutorials and videos:

Single Page Applications 1: Manipulating the Client Side Viewmodel. Discover how both the server, with remote commands, and the User, with UI primitives, can manipulate the client side ViewModel.
Single Page Applications 2: Validation Error Handling. Enhancement to the usual Mvc Client and Server Validation logic, usefull in Single Page Applications: errors bubbling, hidden errors handling, error entities filtering, entity level, and overall model validation.
Single Page Applications 3: TreeIterator. Discover how to change completely the layout of the virtual pages of your Single Page Application, by simply changing the client side ViewModel.
Data Moving Plugin Forms: Detail Views, Data Filtering UI, and Undo/Redo Stack. Data Moving Forms provide standard detail and filter views, but can be customized with any Html. Moreover, all actions performed in edit mode can be undone and re-done with the typical editors undo/ redo buttons.
Data Moving Styling. Discover, how Data Moving controls can be styled. Both Jquery UI and JQuery Mobile styling framework are supported. Moreover, the developer has the option to customize the standard Jquery UI, or JQuery Mobile styling, and to define new styling frameworks. Different styling options can be mixed in the same page, and also in the same control.
Data Moving Controls. A Review of all Data Moving out-of-the-box controls.
Introduction to the Data Moving Plugin. Notde-to-Node Data Binding, Data Interactions, and TreeViews.

Updated Wiki: Data Moving Plug-in Videos and Tutorials

frankabbruzzese — Thu, 18 Apr 2013 08:10:37 GMT

Data Moving Plug-in Tutorials and Videos

The Data Moving Plug-in is in its RC stage, and will be released to the market about the end of April 2013.

Here screenshots of the Data Moving Plug-In on Actual Mobile Devices

Below the list of available preliminary tutorials and videos.

Single Page Applications 1: Manipulating the Client Side Viewmodel. Discover how both the server, with remote commands, and the User, with UI primitives, can manipulate the client side ViewModel.
Single Page Applications 2: Validation Error Handling. Enhancement to the usual Mvc Client and Server Validation logic, usefull in Single Page Applications: errors bubbling, hidden errors handling, error entities filtering, entity level, and overall model validation.
Single Page Applications 3: TreeIterator. Discover how to change completely the layout of the virtual pages of your Single Page Application, by simply changing the client side ViewModel.
Data Moving Plugin Forms: Detail Views, Data Filtering UI, and Undo/Redo Stack. Data Moving Forms provide standard detail and filter views, but can be customized with any Html. Moreover, all actions performed in edit mode can be undone and re-done with the typical editors undo/ redo buttons.
Data Moving Styling. Discover, how Data Moving controls can be styled. Both Jquery UI and JQuery Mobile styling framework are supported. Moreover, the developer has the option to customize the standard Jquery UI, or JQuery Mobile styling, and to define new styling frameworks. Different styling options can be mixed in the same page, and also in the same control.
Data Moving Controls. A Review of all Data Moving out-of-the-box controls.
Introduction to the Data Moving Plugin. Notde-to-Node Data Binding, Data Interactions, and TreeViews.

Updated Wiki: Home

frankabbruzzese — Wed, 17 Apr 2013 16:59:07 GMT

Main object of the project

2013-04-17. Give a look to the Data Moving Plug-In on Actual Mobile Devices

2013-03-22. The data Moving Plugin is in its RC stage and will be released to the market within within the end of April. Take a trip into its amazing features :

See here the complete list of all Data Moving plug-in Tutorials

NEW TO THE MVC CONTROLS TOOLKIT?

See the list of all Data Moving Plug-in Tutorials/Videos here,
See the list of all Mvc Controls Toolkit Tutorials here .
Download complete examples here
See the installation procedure here. Avaliable also NuGet packages:
- Mvc3ControlsToolkit
- Mvc2ControlsToolkit.
See full documentation here.
See Releases History here.
Read about the theory that is behind the Mvc Controls Toolkit here.

FEEL FREE TO CONTACT US:

Would you like to invite us to hold a Conference/Webcast? Contact us
Do you need courses on the Mvc Controls Toolkit? Contact us
Do you need help on a project? Contact us
Do you need a Commercial Licence to distribute a product based on the Mvc Controls Toolkit? Contact us
Do you need Custom Controls? We can develop them for you
Our Rank
Follow us on Twitter
Follow us on Google+
LinkedIn Group of Mvc Controls Toolkit Users

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, See here
Support for Theming. See here.
Complete set of server controls (no need to write any javascript) that handle both the rendering and the binding of the input to the View Model :
- Items Controls
  - Update/Insert/Delete/ Sortable Templated Datagrid (Templated)
  - TreeView
  - Insert/Update/Delete Mouse Dragging Sorting List (Templated)
  - ClientBlockRepeater (Templated)
  - Menu and MenuFor
  - CheckBox list for selecting items (Templated)
  - DualSelect Box for selecting and ordering items
  - Enhanced DropDown extensions with <optgroup> and other nice features.
  - Keywords List: editing a list into a TextBox (Templated)
- Collections Support Controls
- Layout Manipulation Controls
- Simple Controls
  - DateTimeInput and DateRange attribute
  - TypedTextBox
  - TypedEditDisplay
  - Timer Helpers
  - ColumnName Helpers
  - DisplayField Helper
  - Html 5 Inputs
  - Mutual exclusive CheckBoxes
  - GenericInput Helper
- Client Side javaScript functions
- Data Annotations and Validation Attributes with full support for client side validation and globalization See here.
- Action Filters and View Results See here.

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.