Simon MᶜKenzie

@dotnet-policy-service agree On Sat, 18 May 2024, 12:46 pm dotnet-policy-service[bot], < ***@***.***> wrote: > @simonmckenzie the command you issued > was incorrect. Please try again. > > Examples are: >...

Hi @roji, Since the parent issue (#33748) has been put into the backlog pending work on provider-level case-sensitivity settings, this PR is now in an uncertain state. I would argue...

I have raised a pull request for this change (sorry, I missed the part about asking for permission first). My change is very simple - it replaces a `.Except` used...

I had another thought - while I feel my current approach is a very readable solution, if there's any concern about performance (not that I really expect there will be),...

Hi @roji, It's an interesting point about whether EF should be strict around column case, but perhaps that should be a new issue...? My issue is just about the incorrect...

@roji, I know this is just the opinion of a random person on the internet (me), but it seems that while some SQL flavours do allow queries to return multiple...

Hi @ChristianSauer, This PR isn't obsolete - there's still an issue with generic type parameter deduplication. I've rebased, simplified the code, and added another test now the other PR is...

This broke interface generation on one of my classes - I need to investigate further, but it looks like it's because one of the method parameter types was available through...

I was able to reproduce the "broken interface" issue using inheritance: * Assembly 1 * Add class with parameter resolved via a global using * Assembly 2 * Add class...

I can see other cases that also fail, where "using aliases" break the interface generation:  ```csharp...