MigSharp 3.1.3

.NET Framework 4.5 This package targets .NET Framework 4.5. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
dotnet add package MigSharp --version 3.1.3                

                    
                

            
NuGet\Install-Package MigSharp -Version 3.1.3
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="MigSharp" Version="3.1.3" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add MigSharp --version 3.1.3                

                    
                

            
#r "nuget: MigSharp, 3.1.3"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install MigSharp as a Cake Addin
#addin nuget:?package=MigSharp&version=3.1.3

// Install MigSharp as a Cake Tool
#tool nuget:?package=MigSharp&version=3.1.3

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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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.

Version Downloads Last updated
4.0.1 36,724 1/16/2018
3.2.1 3,428 7/7/2017
3.2.0 4,936 11/16/2016
3.1.3 1,394 10/23/2016
3.1.2 1,169 10/23/2016
3.1.1 1,452 8/23/2016
3.1.0 3,003 7/26/2016
3.0.0 7,028 12/17/2015
2.3.4 1,751 11/20/2015

3.1.3
- added support for new (sequential and random) GUID as default value on existing columns too
3.1.2
- added support for new (sequential and random) GUID as default value
- hard-coded public enum member values to not force recompilation of consumers of 3.1.x (SqlServerCe was removed from Platforms in 3.1.0; see: "Robust Programming" section on https://msdn.microsoft.com/en-us/library/sbbt4032.aspx)
3.1.1
BUG FIXES:
- SQL Server: dropping or renaming a default constraint was not prefixing the schema of the corresponding table
- 3.1.0 was wrongly built in our CI environment and was requiring .NET 4.6.1 bindings (string.Format)
3.1.0
- Added support for current UTC datetime as default (#37)
- Added support for current datetimeoffset as default (SQL Server only)
- New API to selectively execute pending migrations (see: IMigrationBatch.RemoveAll)
- Removed support for SQL Server CE (deprecated by Microsoft in 2013)
BUG FIX:
- SQLite: using HavingCurrentDateTimeAsDefault correctly set the date time to local format instead of GMT/UTC
3.0.0
- New API dedicated to schema altering (see: DbAlterer; replaces Migrator.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)