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.
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
Client-Side Blazor OrderByDescending #15259
Labels
Comments
Seems related with #8872 |
using System;
using System.Runtime.InteropServices;
using System.Linq;
public class TestQueryableOrderBy
{
public static void Main (String[] args) {
OnInit();
Console.WriteLine ("Hello, World!");
}
class Pet
{
public string Name { get; set; }
public int Age { get; set; }
}
static void OnInit()
{
Pet[] pets = { new Pet { Name="Barley", Age=8 },
new Pet { Name="Boots", Age=4 },
new Pet { Name="Whiskers", Age=1 } };
var query = pets.AsQueryable().OrderByDescending(pet => pet.Age);
foreach (Pet pet in query)
Console.WriteLine("{0} - {1}", pet.Name, pet.Age);
}
}
I'm seeing the same failure with OrderBy though. |
marek-safar
added a commit
to marek-safar/corefx
that referenced
this issue
Aug 7, 2019
marek-safar
added a commit
to marek-safar/corefx
that referenced
this issue
Aug 8, 2019
marek-safar
added a commit
to mono/corefx
that referenced
this issue
Aug 8, 2019
marek-safar
added a commit
to marek-safar/mono
that referenced
this issue
Aug 8, 2019
marek-safar
added a commit
to marek-safar/mono
that referenced
this issue
Aug 8, 2019
marek-safar
added a commit
that referenced
this issue
Aug 8, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From @matheusjulio96 on Wednesday, June 19, 2019 2:02:04 PM
The bug: Execute an OrderByDescending query throw the error 'Unhandled exception rendering component: System.NullReferenceException: Object reference not set to an instance of an object.'
Steps to reproduce the behavior:
Expected behavior: Execute the query and print the values.
Ps: OrderBy query works fine.
Copied from original issue: dotnet/aspnetcore#11371
The text was updated successfully, but these errors were encountered: