Telerik UI for ASP.NET MVC 6 - RC

[Davide]

Hello,
when will be the support available for RC version?

Best Regards

[Dimiter Madjarov]

Hello Davide,

We are currently supporting the ASP.NET MVC6 RC version. Additional information could be found on our documentation page. Keep in mind that currently not all widget wrappers have been ported for MVC6, so the suite is not yet complete.

Regards,
Dimiter Madjarov
Telerik

[Thomas]

Dimiter:
Do you have a roadmap you can share for when the remaining wrappers will be ported?  Now that we have reached the RC stage with MVC6 I'm hoping to get an idea of when the "interim" releases the documentation speaks of will be made available.

Thanks!

[Sebastian]

Hi Thomas,

Our goal is to port all remaining wrappers till the RTM release of ASP.NET 5, expected in Q1 2016 according to Microsoft (see official roadmap for ASP.NET vNext here).

You may also be interested in reviewing this recent blog post elaborating on our ASP.NET vNext RC1 support for UI for ASP.NET MVC.

Best regards,
Sebastian
Telerik

[Landry]

Hello,

 

It seems to me that default grouping in the grid (using the Group() option in the DataSource) is not working with the RC version.

 

I don't know if this was working in previous versions or not.

 

I was trying to group my grid on a particular column by default without enabling grouping in ui (by setting .Groupable(false) on the grid options)

[Landry]

It seems this was working fine in beta8 so this is a regression in RC1

[Dimiter Madjarov]

Hello Landry,

Thank you for reporting this. I will forward the feedback to the developers team, so they can inspect the behavior further.

Regards,
Dimiter Madjarov
Telerik

[Landry]

Hello,

 

Since RC, I often encounter a problem while debugging a project that references Kendo.MVC.

When I try to debug the project, I can set breakpoints OK, but it is not possible to inspect any variables at all.

 

I get the following error message when trying to inspect any variable:

"An assembly with the same simple name has already been imported" for Kendo.MVC

 

This problem appears really often but not everytime I try to debug the project so it's strange.

 

I think this may be related to the signing of the Kendo.Mvc assembly since ASP.NET 5 change the way it handles assembly signing by default for the framework composents but I am not sure at all.

 

My collegues encountered the same problem.

 

Thanks for your help.

 

[Dimiter Madjarov]

Hello Landry,

Thank you for reporting the problem. Are you experiencing it only in projects with the Kendo.Mvc reference or with other third party libraries too?

Regards,
Dimiter Madjarov
Telerik

[Landry]

Hello,

 

At the moment I only encounter this problem on projects that uses the Kendo.Mvc reference.

But these projects also use other third party libraries such as SimpleInjector, Serilog or Hangfire.

I have not encountered this problem on other projects using other third party libraries only but the thing is I have not tried to create a project with all the same third party libraries as the projects that are encountering this problem with Kendo.Mvc.

[Dimiter Madjarov]

Hello Landry,

At the moment we are unable to reproduce the behavior locally. If we manage to observe it our end, we could provide further assistance, so if you are able to reproduce it in our demos solution or another small project using Kendo.Mvc, you could send it to us here or via the support system, so we could take a look locally.

I wish you a great weekend!

Regards,
Dimiter Madjarov
Telerik

[Landry]

Hello,

 

Here is a simple test solution in wich I encounter the debugging problem. For instance when setting a breakpoint in the Index action of the Home controller, I can't analyse any variable.

[Landry]

The previous solution also demonstrates the default grouping bug reported earlier

[Landry]

In the layout of the previous solution, I specified css fallback using test classes (k-common-test-class and k-theme-test-class) from the lastest bower package (2015.3.1201).

This classes are not available at the moment in the current CDN version (2015.3.1111) so even if the CDN is loading properly, this will presently fallback to local files.

So in the meanwhile (until the CDN are updated), you will have to copy a kendo-ui folder containing js and styles folders to the wwwroot/lib folder of the solution.

[Landry]

otherwise, you could just use theses lines in the meantime:

 

<link rel="stylesheet" href="http://kendo.cdn.telerik.com/2015.3.1111/styles/kendo.common-bootstrap.min.css"
      asp-fallback-href="~/lib/kendo-ui/styles/kendo.common-bootstrap.min.css"
      asp-fallback-test-class="fake" asp-fallback-test-property="color" asp-fallback-test-value="red" />
<link rel="stylesheet" href="http://kendo.cdn.telerik.com/2015.3.1111/styles/kendo.bootstrap.min.css"
      asp-fallback-href="~/lib/kendo-ui/styles/kendo.bootstrap.min.css"
      asp-fallback-test-class="ktb-theme-id-bootstrap" asp-fallback-test-property="opacity" asp-fallback-test-value="0" />

[Landry]

Be aware of the Hosting:Environment that is set to "Development" by default in the solution.

This will not use the CDN unless you change it to "Production" or "Staging".

 

Otherwise, you will have to provide local files for kendo-ui

[Dimiter Madjarov]

Hello Landry,

Regarding the grouping issue, we have reproduced it on our end and it is already fixed. The fix is available in the latest internal build.

As for the debugging problem, it is reproducing on our end too. Running the project manually from a Developer Command Prompt showed the exact reason for it, which is an exception in Microsoft.AspNet.Server.Kestrel.Networking showing an Error -4091 EADDRINUSE address already in use. According to the information in the aspnet GitHub repository, it is a known issue, which is currently being fixed by Microsoft. It is not related to Kendo UI, but a solution that worked on my end was to manually kill all dnx.exe processes from Windows Task Manager.

Regards,
Dimiter Madjarov
Telerik

[Landry]

Hi,

 

Thank you for your answer.

 I'll be looking for the new update with the fix for default grouping.

 

Regarding the debugging problem, how did you proceed exactly in order for it to work with Visual Studio?

When I stop all dnx.exe processes before startint the project with debugging in Visual Studio I still can't inspect any variables while debugging.

[Dimiter Madjarov]

Hello Landry,

The same approach worked on our end. I am not sure how exactly to resolve the issue on your end, as it is not specifically related to Kendo UI. I would suggest to forward the problem to the aspnet issue tracker, where you will receive more prompt assistance.

Regards,
Dimiter Madjarov
Telerik

[Landry]

Hello,

 

It seems it is not possible at the moment to define a custom filter control for a column of our choice in a Kendo grid.

 

I tried this:

columns.Bound(p => p.ProductName).Filterable(x => x.UI(@<text>function(e){ alert('plop'); }</text>));

[Landry]

I also tried this:

columns.Bound(p => p.ProductName).Filterable(x => x.UI("myCustomFilter"));
...
<script type="text/javascript">
    function myCustomFilter(e) {
        alert('plop')
    }
</script>

and this when trying to define custom format for date filter:

 

columns.Bound(p => p.ExpiryDate).Filterable(x => x.UI(@Html.Kendo().DatePicker().Name("testDatePicker").Value("#=ExpiryDate#").Format("{0:dd MMM yy}").ToHtmlString()));

 

But I could never see the alert firing...

 How I am supposed to do this? Is it a bug in the RC? 

 

 

columns.Bound(p => p.ProductName).Filterable(x => x.UI("myCustomFilter"));

...

<script type="text/javascript">

    function myCustomFilter(e) {

        alert('plop')

    }

</script>

[Landry]

Hello Dimiter,

 

Regarding the debugging problem, it would be great if you could detail the process you went through in order to solve the problem on your end (your workaround).

 

I understand your point about the problem coming from the kestrel server and not from the Telerik components.

But I would really appreciate it if you could share the details of your workaround procedure as I am not sure if I tried the right thing in order to use the workaround you described.

 

This is what I have done so far:

• Open Visual studio
• Open the project where I am encountering the debugging problem
• Define a breakpoint in the project where I want to try debuggig
• Run the project with debugging enabled
• Use the application to the point of reaching the breakpoint (I am reaching it just fine in Visual Studio)
• (at this point, there are 2 dnx.exe processes started, one for IISExpress that runs the application and one for Visual Studio Debugging)

What should I do from this point onward?

If I kill the wrong dnx.exe processus (the one for debugging in VS), the debugging just stops and I am back to point 0.

If I kill the other dnx.exe processus, it just restarts on its own and I still can't inspect any variables in VS on the current breakpoint.

 

Please share with me some pointers as how you made this work.

[Dimiter Madjarov]

Hello Landry,

We were unable to reproduce the filterable customization problem on my end. We have a demo, which demonstrates the same approach in our MVC 6 demo solution. It is called "Filter Menu Customization". Are you reproducing the same issue on the demo as well?

Regarding the debugging issue, the approach that worked on my end was to kill the dnx.exe processes before starting the debug of the current project. This will start a new dnx.exe process. After that, the only thing needed was to start the debugging of the project.

Regards,
Dimiter Madjarov
Telerik

[Landry]

Hello Dimiter,

 Here is a working solution where you can reproduce the filterable customization problem when trying to customize the filter controls.

 It seems that this problem only appears when using the row filter mode. As the demo is using the menu filter mode, it does not have this problem.

 

Also, in the provided solution, I demonstrated another problem I encountered: filterable customization for allowed operators works well when defining it on a particular column, but does not work when configured at grid level for all columns of the designated type.

 

Regarding the debugging problem, unfortunately I could not male the workaround work. Let's hope Microsoft correct this problem soon enough.

[Dimiter Madjarov]

Hello Landry,

The filterable UI configuration option is only used when the filter mode is set to menu. If you would like to customize the appearance of the filter input when the mode is set to row, only the filterable Cell configuration should be used e.g. columns.filterable.cell.template.

Regarding the listed operators, the correct ones are displayed for the date column in the provided solution, even when configured on Grid level. The other columns display all of the operators, because the current configuration applies only to columns of type "date".

As a side note, since the current topics got shifted away from the initial problem discussed in this forum thread, I would like to suggest to open a separate (or multiple) ones if further problems appear, so we could easily resolve each one in a separate thread. Thanks for the understanding.

Regards,
Dimiter Madjarov
Telerik

[Dmitry]

[quote]

"An assembly with the same simple name has already been imported" for Kendo.MVC

[/quote]

Workaround working for me:

In Visual Studio 2015 > Tools > Options > Debugging > General we have marked options:

-Use Managed Compatibility Mode
-Use the legacy C# and VB expression evaluators

(from http://stackoverflow.com/questions/35536726/error-cs1704-in-aspnet-mvc-razor-and-dnx-1-0-0-rc1-update1-clr-x86)