If I have a field defined as @Html.Kendo().TextBoxFor(m => m.Customer.CustomerNumber) then my complex property in my model will be correctly used. If however if add a name value i.e. @Html.Kendo().TextBoxFor(m => m.Customer.CustomerNumber).Name("CustNum") so that I can reference this field in javascript then this name takes precendence as the property name and as such the property in my model is not used. If we are using the 'For' version of an input field where we have already identified the property can this take precedence over using the Name field. That way we can simple names for use in the Javascript and yet still use complex properties.

in the option from Grid this feature is missing

When using Html.Kendo().DeferredScripts() possibly bundle all the controls initialization in one single jQuery initialization function, instead of a call for each of the deferred controls.

For R# action annotations details please check the following link - http://blogs.jetbrains.com/dotnet/2011/12/providing-intellisense-navigation-and-more-for-custom-helpers-in-aspnet-mvc/

And regarding additional actions for url builders - usually I have the action which provides the data for the grids in the same controller so I would prefer to write "... .Read(read => read.Action("LoadSitesData", new { id = Model.StudyId })" instead of "... .Read(read => read.Action("LoadSitesData", "StudySitesAdministration", new { id = Model.StudyId })"

Given the release of ASP.NET and Web Tools 2012.2, is it possible to create custom project templates.

It will be extremely nice if we can get editor intelligence with kendoui widgets when using plain JS, specially with the template engine.

Some simple examples about this can be found at the end of thhis article.

http://www.hanselman.com/blog/ReleasedASPNETAndWebTools20122InContext.aspx

have an option on the grids where it does not defualt to the  date/local time. Users are asking for the same time to display across time zones.
I use the workaround but we still have issues with it.

Implement kenfo.confirm with title

[Applied through to MVC]
For entering data in the grid it will be great to have the grid be able to maintain the cell position when updates are triggered through the grid. 

So that after the update, for all cases (batch, autosync, scrollable, etc), the position in the grid is maintained and navigatable through common keyboard actions such as: tabbing to the next, shift+tab to the previous, etc.

The main goal being for users to have an easy and smooth time navigating the grid and making edits without having their default position wiped and view jerked to another position in the grid after a save/databind/sync is made. 

A high value case for this is when both autosync and scrollable are turned on; though it will certainly bring value to users and their user experience for a great many usage cases.

It is a disappointing surprise for a 3rd party tool to not have this functionality.

With the current version available from the DLL it will be possible to simplify bundling and include of CSS and JS files. I currently do something along the lines of

    //BundleConfig.cs
        var version = typeof(Kendo.Mvc.UrlGenerator).Assembly.GetName().Version;
        var kendoVersion = string.Format("{0}.{1}.{2}", version.Major, version.Minor, version.Build);
 
 
        bundles.Add(new StyleBundle("~/Content/kendo/"+kendoVersion+"/css").Include(
            "~/Content/kendo/"+kendoVersion+"/kendo.common.min.css",
            "~/Content/kendo/"+kendoVersion+"/kendo.default.min.css"
            ));
 
        bundles.Add(new ScriptBundle("~/Scripts/kendo/" +  kendoVersion +"/scripts").Include(
            "~/Scripts/kendo/" + kendoVersion + "/kendo.all.min.js",
            "~/Scripts/kendo/" + kendoVersion + "/kendo.aspnetmvc.min.js",
            "~/Scripts/kendo/" + kendoVersion + "/cultures/kendo.culture.en-GB.min.js"
            ));

And similarly in the views. Getting the version directly from the DLL without hacking around in Assembly.GetName.Version and string manipulation will make this clearer. I'd also suggest you update the documentation to reflect this pattern.

As its a new method/getter, it is not a breaking change.

At present to get the nice kendo checkboxes you need a checkbox followed by a label, you can't do this in asp.net mvc because

@Html.CheckBoxFor(x => x.IsEnabled)

renders as:

<input id="IsEnabled" type="checkbox" value="true" name="IsEnabled">
 <input type="hidden" value="false" name="IsEnabled">

The solution is to use the kendo mvc dll, or possibly just make your own, but it would be much easier if the kendo ui code could just ignore the hidden input, or if the two controls could be linked via 'for', 'data-for', 'data-whatever'

Please take a look at this issue where DDLs and CoboBoxes won't submit their values the second time after validation fails and the required field is entered.
This was reported back in 2015 and is still unresolved. 
https://www.telerik.com/forums/kendo-validation-does-not-work-the-second-time

I would expect a fluent method chain to not produce side effects when a method is invoked more than once.  particularly, concerning the ability to apply HtmlAttributes more than once to a method chain.  This prevents me from implementing meaningful extension methods to promote a DRY approach to views. 

In particular, I am trying to do something like this:

public static TextBoxBuilder<TProperty> PasswordFor<TModel, TProperty>(this WidgetFactory<TModel> widgetFactory, Expression<Func<TModel, TProperty>> expression)
        {
            return widgetFactory.TextBoxFor(expression).HtmlAttributes(new { type = "password" });
        }

        public static TextBoxBuilder<TModel> AutoFocus<TModel>(this TextBoxBuilder<TModel> builder)
        {
            return builder.HtmlAttributes(new { autofocus = true });
        }


I am finding that because the HTML attributes is cleared in your base implementation.. 

this.Component.HtmlAttributes.Clear();


it doesn't support an aggregation of attributes, but instead it's last-man-in.   that defeats the purpose of extensibility and effectively insists upon repetition and sort of brittle design that a copy/paste architecture results in.

I would believe it be completely acceptable to give the last-attribute-applied precedence and overwrite the value, but the reality is that we're talking about basic key/value pairs, and it shouldn't be difficult to merge the attributes as they are built.   best case, right now i have to implement my own derivation of the WidgetBuilderBase and implement an extension method off the WidgetFactory that bootstraps my functionality - certainly not a stretch, but more work than should probably be necessary.



   
    public virtual TBuilder HtmlAttributes(object attributes)
    {
      return this.HtmlAttributes(ObjectExtensions.ToDictionary(attributes));
    }

    public virtual TBuilder HtmlAttributes(IDictionary<string, object> attributes)
    {
      this.Component.HtmlAttributes.Clear();
      Kendo.Mvc.Extensions.DictionaryExtensions.Merge(this.Component.HtmlAttributes, attributes);
      return this as TBuilder;
    }

I want tree view all of it to be listed without mouse or click ,and to be as list of items that tree view list them
what im saying i have list ,i pass it to tree view,tree view display all with all its sub trees
without click or mouse over

need button for downloading files from file browser in telerik ui for mvc/kendo mvc

thanks

When using QueryableExtensions.ToDataSourceResult() from Telerik MVC, SQL following gets produced:

.. FROM [RMP].[V_UC_EQUIPMENT_LOG2_LOCALIZATION] WHERE ([Extent1].[LOG_TIME] >= convert(DateTimeOffset, ''2019-03-05 23:00:00.0000000 +00:00'', 121)) AND ([Extent1].[LOG_CLASS_ID] IN (78,7,18,30,19,16,17))

When we filter manually in code with linq, e. g.

..  table.Where(e => e.T_EquiID == 234234) ...

the linq provider produces a parameterized query as follows:

AND (@p__linq__0 = [Extent1].[T_EquiID])...

When using a parameterized query, Sql Server can reuse the execution plan much better saving compile time, which is in our case sometimes a big issue.

Please tell us, why can QueryExtensions do produce parameterized queries.

There should be capabilities to group parent resources to selected child resources

Currently the Scheduler groups all child resources under each parent resource.
Example Resources:
Parent resources: New York Tennis Club, California Tennis Club
Child Resources: Court 1, Court 2, Court 1, Court 2, Court 3, Court 4

Currently the Scheduler groups parent and child resources as:
- New York Tennis Club is grouped with Court 1, Court 2, Court 1 and Court 2, Court 3, Court 4
- California Tennis Club is grouped with Court 1, Court 2, Court 1, Court 2, Court 3 and Court 4

I would like the capability to group parent resources with selected child resources, in my situation im trying to achieve this structure of grouping:

Desired Grouped Resources:
- New York Tennis Club is grouped with Court 1 and Court 2
- California Tennis Club is grouped with Court 1, Court 2, Court 3 and Court 4.

If you look at the Syncfusion Scheduler, they have this feature, it would be nice if the Telerik/Kendo Scheduler could do this..

If you look at the link i provided below, you can see that the Syncfusion Scheduler allows multiple resource groups which has the capability to group parent resources to selected child resources.

Syncfusion Scheduler Demo shows:
Room 1 is grouped to Nancy and Michael
Room 2 is grouped with Steven

http://mvc.syncfusion.com/demos/web/schedule/resourcegrouping

Take the look and feel of the UI for IOS gauges, for instance the linear gauge, and duplicate that into a more customizable gauge tool set.

Particularly, the ability to gradient linear gauges, remove ticks and round the edges. Similar to a progress bar with a value marker.

I need configure in my Razor View, with my Multiselect helper, the maxselectedItems property (like others properties: MinLength, Filter,etc)

Hi, 

I'm wondering that if it's too much trouble for Telerik to add/implement  Persian Calendar In Kendo UI Products.

respectfully,

Thank you for your consideration,

Currently <EditorName>For is not available for the DateInput wrapper. This feature is available for the other editors.