Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1066321
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T19:59:49+00:00 2026-05-16T19:59:49+00:00

This question ( LINQ and a natural sort order… ) talks about how to

  • 0

This question (LINQ and a natural sort order…) talks about how to implement natural sorting in Linq using an IComparer. I’ve used this successfully in the past with IEnumerables, but I am unable to make it work in Linq-to-SQL expressions. Is this because the specific overload of .OrderBy() that takes an IComparer is not supported by Linq-to-SQL?

If this is in fact the case, are there any practical workarounds?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T19:59:50+00:00Added an answer on May 16, 2026 at 7:59 pm

    It’s not that the IComparer is not supported, it is that in Linq-to-Sql, an OrderBy() must be translated to a T-Sql operation. If it allows you to specify criteria for comparisons, The C# code behind it would have to be executed by SQL server to use it.

    If you need to do something in Linq-To-Sql that is not supported but which can be done in T-SQL, you can always get around it by using a stored procedure, which work splendidly with Linq-to-Sql. If that it inconvenient, you can call the ToList() method to invoke the execution and then sort it in memory. The practicality of this depends on the size of the data and how much of it you wished to fetch (such as when implementing pagination).

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.