Bug description
This only occurs when running a migration on Linux. Windows appears to be ok with this. I am currently testing this in WSL2 with the Ubuntu distro. When I run my test suite on WSL2 I get the PendingModelChangesWarning. I have added a migration and found that its a diacritic unicode character that isn't recognised as being a match. The output of the migration is shown in the code section.
I recognise that this isn't technically a dotnet ef bug, but I don't know how the diff occurs in order to fix it on my environment and would like to know a solution. Hopefully making this useful for someone else. I have gone through the other issues, but I cannot find a similar issue.
Your code
using Microsoft.EntityFrameworkCore.Migrations;
#nullable disable
namespace XXXX.Migrations
{
/// <inheritdoc />
public partial class Test : Migration
{
/// <inheritdoc />
protected override void Up(MigrationBuilder migrationBuilder)
{
migrationBuilder.UpdateData(
table: "BusinessTypes",
keyColumn: "BusinessTypeId",
keyValue: 28,
column: "WebDescription",
value: "Caf�");
migrationBuilder.UpdateData(
table: "BusinessTypes",
keyColumn: "BusinessTypeId",
keyValue: 29,
column: "WebDescription",
value: "Caf� & bar");
}
/// <inheritdoc />
protected override void Down(MigrationBuilder migrationBuilder)
{
migrationBuilder.UpdateData(
table: "BusinessTypes",
keyColumn: "BusinessTypeId",
keyValue: 28,
column: "WebDescription",
value: "Café");
migrationBuilder.UpdateData(
table: "BusinessTypes",
keyColumn: "BusinessTypeId",
keyValue: 29,
column: "WebDescription",
value: "Café & bar");
}
}
}Stack traces
Verbose output
EF Core version
10.0.0
Database provider
No response
Target framework
No response
Operating system
Windows 11 & WSL2.0 Ubuntu
IDE
Visual Studio 2026 18.5.2
Bug description
This only occurs when running a migration on Linux. Windows appears to be ok with this. I am currently testing this in WSL2 with the Ubuntu distro. When I run my test suite on WSL2 I get the PendingModelChangesWarning. I have added a migration and found that its a diacritic unicode character that isn't recognised as being a match. The output of the migration is shown in the code section.
I recognise that this isn't technically a dotnet ef bug, but I don't know how the diff occurs in order to fix it on my environment and would like to know a solution. Hopefully making this useful for someone else. I have gone through the other issues, but I cannot find a similar issue.
Your code
Stack traces
Verbose output
EF Core version
10.0.0
Database provider
No response
Target framework
No response
Operating system
Windows 11 & WSL2.0 Ubuntu
IDE
Visual Studio 2026 18.5.2