Dynamic LINQ: retarget net10.0, System.Linq.Dynamic.Core 1.7.4, Program.cs prints the article's outputs - #2227
Open
vladimir-pecanac-main wants to merge 1 commit into
Conversation
…am.cs prints the article's outputs - Both projects net6.0 to net10.0. - System.Linq.Dynamic.Core 1.2.21 to 1.7.4. 1.2.21 sits inside both published advisory ranges: GHSA-w65q-jcmv-28gj / CVE-2023-32571 (critical, CVSS 9.8, >= 1.0.7.10 and < 1.3.0) and GHSA-4cv2-4hjh-77rx / CVE-2024-51417 (high, < 1.6.0). - Test packages: Microsoft.NET.Test.Sdk 18.10.1, NUnit 4.6.1, NUnit3TestAdapter 6.3.0, NUnit.Analyzers 4.15.0, coverlet.collector 10.0.1. No assertion changes. - Program.cs now prints the projection, the multi-property sort and the combined lambda filter that the article quotes, so its output blocks can be re-run.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates the sample behind https://code-maze.com/using-dynamic-linq/.
Both projects move from net6.0 to net10.0.
System.Linq.Dynamic.Core goes from 1.2.21 to 1.7.4, the current stable release on NuGet (read 2026-09-23). 1.2.21 sits inside both published advisory ranges for the package, and 1.7.4 sits outside both, per the GitHub Advisory Database re-queried today:
Test packages go to current stable, re-queried on NuGet the day this PR opened: Microsoft.NET.Test.Sdk 18.10.1 (the batch policy named 18.10.0; the re-query found 18.10.1 and that is what ships), NUnit 4.6.1, NUnit3TestAdapter 6.3.0, NUnit.Analyzers 4.15.0, coverlet.collector 10.0.1. NUnit stays the test framework for this folder, and no assertion changes: Assert.AreEqual and Assert.NotNull compile on NUnit 4.6.1 with 0 warnings.
Program.cs used to print only "Application Started". It now instantiates TestData and prints the three results the article quotes: the Name and Department projection, the "Department desc, Name" sort, and the combined ParseLambda filter. The article's output blocks now have a source that can be re-run. TestData.cs is unchanged.
Verified on SDK 10.0.302 against runtime 10.0.10: dotnet build -c Release is 0 errors and 0 warnings, dotnet test is 25 of 25 passing, and dotnet list package --vulnerable --include-transitive reports no vulnerable packages in either project.
Only this article's folder is touched.