MigSharp 3.0.0
See the version list below for details.
dotnet add package MigSharp --version 3.0.0
NuGet\Install-Package MigSharp -Version 3.0.0
<PackageReference Include="MigSharp" Version="3.0.0" />
paket add MigSharp --version 3.0.0
#r "nuget: MigSharp, 3.0.0"
// Install MigSharp as a Cake Addin #addin nuget:?package=MigSharp&version=3.0.0 // Install MigSharp as a Cake Tool #tool nuget:?package=MigSharp&version=3.0.0
Write database migrations and/or schema modifications in your favorite .NET language and let Mig# generate the platform-dependent SQL code and update your schema. Features: fluent interface, automatic versioning, multi-module support, scripting to SQL files, validation framework for portability issues, suport for SQL Server, Oracle, MySQL, Teradata, SQLite, legacy integration
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET Framework | net45 is compatible. net451 was computed. net452 was computed. net46 was computed. net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
This package has no dependencies.
NuGet packages (2)
Showing the top 2 NuGet packages that depend on MigSharp:
Package | Downloads |
---|---|
CMS.Domain
Description |
|
CMS.Framework
Description |
GitHub repositories
This package is not used by any popular GitHub repositories.
3.0.0
- New API dedicated to schema altering (see: DbAlterer; replaces Migritor.BypassMigration)
- Support for SQL Server Schemata (#33)
- Migrations can specify to use their Module name as the default schema
- Versioning table can reside in a custom schema too
- Generate.exe reads out schema names too
- Keeps tracks of ordering of commands even when return types are stored in variables (#60)
- Migration metadata is exposed on the callback context
- Mig# now targets .NET 4.5
BREAKING CHANGES:
- IMPORTANT: database platforms to be included in compatibility validations must be specified explicitly in the options. Mig# cannot (and therefore should not) make any assumptions about your setup.
- A new type called DbPlatform has been introduced to specify database platforms (replaces ProviderNames); providers are now identified by platform, major version, and driver
Note: Mig# uses "Semantic Versioning" http://semver.org/ (by Tom Preston-Werner)