This is a migrated thread and some comments may be shown as answers.

Telerik UI for ASP.NET MVC 6 - RC

25 Answers 211 Views

General Discussions

This is a migrated thread and some comments may be shown as answers.

25 Answers, 1 is accepted

answered on 02 Dec 2015, 09:20 AM

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.

answered on 04 Dec 2015, 10:58 AM

demobugkendogridrc1.zip

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.

answered on 04 Dec 2015, 11:13 AM

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" />

answered on 08 Dec 2015, 09:22 AM

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

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items

answered on 15 Dec 2015, 09:35 AM

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>

answered on 15 Dec 2015, 09:52 AM

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.

answered on 17 Dec 2015, 09:22 AM

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

answered on 17 Dec 2015, 03:20 PM

demobugkendogridrc1.zip

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.

answered on 21 Dec 2015, 12:35 PM

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