Browse Source

Merge pull request #18755 from abpframework/EngincanV-patch-1

Update migration guide for v8.0 (add a note for sql server users)
pull/18757/head
maliming 2 years ago
committed by GitHub
parent
commit
5e9d142466
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 10
      docs/en/Migration-Guides/Abp-8_0.md

10
docs/en/Migration-Guides/Abp-8_0.md

@ -125,9 +125,17 @@ From this version on, instead of injecting the `DaprClient` directly, using the
The documentation is already updated according to this suggestion and can be found at https://docs.abp.io/en/abp/8.0/Dapr/Index. So, if you want to learn more you can check the documentation or see the PR: https://github.com/abpframework/abp/pull/18117.
## Use Newer Versions of the SQL Server (SQL Server 14+)
Starting with EF Core 8.0, EF now generates SQL that is more efficient, but is unsupported on SQL Server 2014 and below. Therefore, if your database provider is SQL Server, then ensure that it's newer than SQL Server 2014. Otherwise, you may get errors due to database creation or while seeding initial data.
The error is similar to: `Microsoft.Data.SqlClient.SqlException (0x80131904)`.
> Check the [Entity Framework Core's Breaking Changes](https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-8.0/breaking-changes#high-impact-changes) documentation for more info.
## Angular UI
# Guards
### Guards
From Angular Documentation;

Loading…
Cancel
Save