Test with VB/F# to make sure expression tree differences are handled

[ajcvickers]

This is in particular reference to removal of Relinq since it was doing some normalization in this area.

• [x] VB string equality/comparison, #19681

[bricelam]

These re-linq transformations handled things like this.

[ajcvickers]

Note from triage: add a cross-language functional tests project.

[bricelam]

I've added a VB test suite with coverage for things that we've fixed (string comparisons and checked arithmetic).

We still have a few known bugs:

• https://github.com/dotnet/efcore/issues/27202
• https://github.com/dotnet/efcore/issues/29185
• https://github.com/dotnet/efcore/issues/30773

But I think we can say that the VB part of this issue is done.

[gaglia]

Hi,

Is there any news regarding this problem?

We are testing with EF 8 and still encounter the same problems. The problem is very impactful in our opinion, we have just finished a huge migration work from Entity Framework 4 to .NET 8 + EF 8 but we are experiencing big problems for certain queries due to these mistranslations for VB.NET

Thank you

[roji]

@gaglia this is a general issue tracking improving testing for VB/F# - please vote on specific translation issues so that we know what you're blocked by. See the issues linked to just above; if you're running into something that isn't already covered, please open a new issue with a minimal code sample that shows the problematic query.

[gaglia]

Hi @roji

I'm experiencing the same problem already reported in issue #31578.

Wrong translation of WHERE with simple filters for string fields

If you need any other information, just let me know. Thank you

[roji]

@gaglia then be sure to vote on #31578, which currently has just one vote - that's a big part of how we choose which issues to prioritize.