Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion NovinCRM.csproj
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@

<!-- External NuGet packages -->
<ItemGroup>
<PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="9.*" />
<PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="10.*" />

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Keep the EF Core packages on the same major version

This bumps only the SQL Server provider to EF Core 10 while the adjacent Microsoft.EntityFrameworkCore.Design and Microsoft.EntityFrameworkCore.Tools references remain pinned to 9.*. Microsoft’s EF Core package-version guidance says all Microsoft.EntityFrameworkCore.* packages shipped by Microsoft must use the same version (https://learn.microsoft.com/en-us/ef/core/what-is-new/nuget-packages#package-versions); with this mix, developers running migrations/scaffolding or Visual Studio EF tooling will load 9.x design-time tooling against the 10.x runtime/provider, which is an unsupported version mismatch. Please update the design/tools packages with the provider.

Useful? React with 👍 / 👎.

<PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="9.*" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="9.*" />
<PackageReference Include="Blazor.PersianDatePicker" Version="3.7.2" />
Expand Down
Loading