In ASP.NET Core MVC 8.0 with KendoUI 2024.1.130, when rendering a page which contains a grid via the taghelper, if the application has enabled Razor runtime compilation, an exception will be thrown within Microsoft.AspNetCore.Razor.Language in Microsoft.AspNetCore.Razor.StringSegment.Equals. Full stack trace attached. This did not occur with ASP.NET Core MVC 6 and KendoUI 2022.3. Attached is a small sample app demonstrating the problem; navigating to the grid page will fail with an exception unless AddRazorRuntimeCompilation is commented out.
A couple levels up the call stack from where the exception occurs, Razor is iterating over descriptor.BoundAttributes; one of these whose DisplayName is "System.Collections.Generic.IDictionary<System.String, System.String> Kendo.Mvc.TagHelpers.GridTagHelper.Templates" has a Name property of null which is what results in the exception.
1 Answer, 1 is accepted
Hi Bill,
Thank you for the thorough information you have shared.
I am sure your input will be very helpful to community members who face the same issue.
With that being said, after some research I was able to conclude that the reported behavior is indeed a bug. Consequently, I've logged a Bug Report in our public Feedback Portal. You can follow the Bug Report here.
Finally, as a token of gratitude for your help to identify the discussed faulty behavior I have updated your Telerik points.
Regards,
Stoyan
Progress Telerik
Rank 1
Iron
Has there been any progress on this bug as I too am experiencing it with version 2024.1.319 but, oddly, only in local debug.
As an additional note, it appears the header alignment logic is also not working when we do something like this:
header-html-attributes='new Dictionary<string,object> { ["class"]="text-end" }'
Hello Bill,
Thank you for your report.
We are aware of the issue and an investigation on the matter is ongoing.
In that context your debugging insights are much appreciated.
I will let you know, when more information is available.
This actually started happening with version 2023.2.606, I kept rolling back versions until I found one that didn't throw the exception. Other controls we use seem unaffected; we are just having an issue with the Grid control.
It took me a few hours today to track this down. I wish I would've seen this post sooner.
Hi,
I'm happy to let you know that a fellow developer subject matter expert has proceeded with the initiative of rectifying the reported behavior by providing a fix candidate. It is currently pending review by our Quality Assurance Engineers.
Hi Mike,
Currently, we do not have an estimate on whether the fix will be released. However, what I can personally do is raise the awareness of this item in order to triage the item for testing.
Hi Bill,
I understand your cause of frustration on this one. I will forward this feedback to my manager, in order to see whether we can speed up and prioritize testing and release for the fix candidate. Since this seems to be a blocker for other customers as well.