starred/radzen-blazor
1
0
Fork 0
mirror of https://github.com/radzenhq/radzen-blazor.git synced 2026-02-04 05:35:44 +00:00
Code Issues 1.3k Packages Projects Releases 22 Wiki Activity

System.Linq.Dynamic.Core Conflict #1659

New Issue
Closed
opened 2026-01-29 17:56:54 +00:00 by claunia · 1 comment
claunia commented 2026-01-29 17:56:54 +00:00
Owner
Copy Link

Originally created by @derekwelton on GitHub (Mar 6, 2025).

Describe the bug
I have a Web API that host a blazor web assembly app. I am using the Dynamic Linq nuget package as well as Radzen. Dynamic Linq is reference in my API, and Radzen is in my web assembly project. Since its hosted, the Web API has access to Radzen.

Within the radzen library, exists a static class called "DynamicExtensions" using the namespace: System.Linq.Dynamic.Core. I wanted to use the Dynamic Linq library functions for "OrderBy", but it is defaulting to the Radzen version. I did not know this until the latest Radzen version 6.2.3 where you made changes to the "OrderBy" resulting in my ef core queries throwing an exception.

I solved this by switching from
query.OrderBy("value")
and switched it to
DynamicQueryableExtensions.OrderBy(query,"value");

My recommendation is to change the namespace for 'DynamicExtensions' to something else to avoid this conflict. Dynamic Linq is a very popular library and believe they have more right to that namespace, but that's my opinion.

I solved my issue so this is more of a suggestion rather than a bug report.

Originally created by @derekwelton on GitHub (Mar 6, 2025). **Describe the bug** I have a Web API that host a blazor web assembly app. I am using the Dynamic Linq nuget package as well as Radzen. Dynamic Linq is reference in my API, and Radzen is in my web assembly project. Since its hosted, the Web API has access to Radzen. Within the radzen library, exists a static class called "DynamicExtensions" using the namespace: System.Linq.Dynamic.Core. I wanted to use the Dynamic Linq library functions for "OrderBy", but it is defaulting to the Radzen version. I did not know this until the latest Radzen version 6.2.3 where you made changes to the "OrderBy" resulting in my ef core queries throwing an exception. I solved this by switching from `query.OrderBy("value")` and switched it to `DynamicQueryableExtensions.OrderBy(query,"value");` My recommendation is to change the namespace for 'DynamicExtensions' to something else to avoid this conflict. Dynamic Linq is a very popular library and believe they have more right to that namespace, but that's my opinion. I solved my issue so this is more of a suggestion rather than a bug report.
claunia commented 2026-01-29 17:56:54 +00:00
Author
Owner
Copy Link

@enchev commented on GitHub (Mar 7, 2025):

Thanks @derekwelton. We needed explicitly to do that since we relied heavily on that library - no longer after 6.x. Check this thread for reference:
https://forum.radzen.com/t/just-released-our-new-major-version-of-radzen-blazor-6-0-0-without-reference-to-system-linq-dynamic-core-nuget-package/19748?u=enchev

@enchev commented on GitHub (Mar 7, 2025): Thanks @derekwelton. We needed explicitly to do that since we relied heavily on that library - no longer after 6.x. Check this thread for reference: https://forum.radzen.com/t/just-released-our-new-major-version-of-radzen-blazor-6-0-0-without-reference-to-system-linq-dynamic-core-nuget-package/19748?u=enchev
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
good first issue
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/radzen-blazor#1659
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?