Kros.KORM.Extensions.Asp 2.0.1

Merge pull request #27 from JanoSlivka/refactor/nugetVersions

Update packages to .NET8.

Kros.KORM.Extensions.Asp 2.0.0

Changes

• Targets .NET 8.

Kros.KORM.Extensions.Asp 1.3.1

Bug fixes

• Downgrade System.Text.Json to 4.7.2. (by @satano in #24)

Kros.KORM.Extensions.Asp 1.3.0

New features

• Use latest Kros.KORM (4.1.0): support for record types and Int64 ID generators.

Kros.KORM.Extensions.Asp 1.1.0-alpha.7

Changes

• Add SourceLink @satano (#19)

Kros.KORM.Extensions.Asp 1.1.0-alpha.6

• Replace System.Data.SqlClient with Microsoft.Data.SqlClient: https://devblogs.microsoft.com/dotnet/introducing-the-new-microsoftdatasqlclient/
• .NET Core 3, update packages
• Support appsettings.local.json

Kros.KORM.Extensions.Asp 1.1.0-alpha.5

Added JsonConverter for converting entities to/from JSON string.

Kros.KORM.Extensions.Asp 1.1.0-alpha.4

KORM settings are separated from connection string.

"ConnectionStrings": {
  "DefaultConnection": "server=servername\\instancename;initial catalog=database"
}

"KormSettings": {
  "DefaultConnection": {
    "AutoMigrate": true
  }
}

Kros.KORM.Extensions.Asp 1.1.0-alpha.3

New Features

• Migrations middleware supports multiple databases. To migrate specific database, add its name to the URL: /kormmigration/dbname. If the name is not specified (middleware is called with just /kormmigration URL), deafult connection string name will be used: DefaultConnection.

Breaking Changes

• Endpoint URL for migrations is /kormmigration to make it consistent with documentation (was /kormmigrate before).

Kros.KORM.Extensions.Asp 1.1.0-alpha.2

New Features

Support for multiple databases/connection strings.

It is possible to add multiple databases to DI container using AddKorm extension methods. Every database is identified by its name. If connection string is in appsettings.json, the name of the database is the same as the name of connection string.

Database can be retrieved by name using IDatabaseFactory - which should be used as a dependency in services.

The first database added to service collection can be retrieved as IDatabase dependency. So if just one database is used, there is no need using IDatabaseFactory.

Breaking Changes

Sections ConnectionString and KormMigrations in appsettings.json are not used anymore. All information about connection strings are in standard ConnectionStrings section as key-value pairs (name - connection string).

Special KORM settings can be set in connection string itself, so the connection string may look:

"ConnectionStrings": {
  "DefaultConnection": "Server=servername\\instance; Initial Catalog=databasename; Integrated Security=true; KormAutoMigrate=true"
}

• Automatic migrations can be set as key KormAutoMigrate with boolean (true/false) value.
• SQL provider key name is KormProvider. It is not needed, the default Microsoft SQL Server provider will be used.