Skip to content

.NET Core 3.1, EF LINQ performance, Library updates #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Jul 30, 2020
Merged

.NET Core 3.1, EF LINQ performance, Library updates #5

merged 2 commits into from
Jul 30, 2020

Conversation

fouadgm
Copy link

@fouadgm fouadgm commented Jul 29, 2020 •
edited
Loading

  1. Updated .NET Core and EF Core versions from 3.0 to 3.1
  2. Updated JS/CSS libraries.
  3. Updated DatatableModels with reference to DataTables "Server-side processing" Manual for v1.10.21
  4. Modified EF LINQ calls to not pull all results for in-memory processing (verified by SQL Server Profiler - Your getting the full recordset every time? #2)
  5. Modified code to utilize DtResult object.

fouadgm added 2 commits July 29, 2020 11:32
@fouadgm
Updated JS/CSS libraries.
ecb0f03
@fouadgm
Updated .NET Core and EF Core versions from 3.0 to 3.1
0ebc321 
Updated DatatableModels with reference to DataTables "Server-side processing" Manual for v1.10.21
Modified EF LINQ calls to not pull all results for in-memory processing (verified by SQL Server Profiler).
Modified code to utilize DtResult object.
@DavidSuescunPelegay DavidSuescunPelegay merged commit f0b8c25 into DavidSuescunPelegay:master Jul 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@fouadgm @DavidSuescunPelegay