Upgrading prerelease Kraken to Kraken 1.1.0

Kraken's official release introduces .NET Core 1.1 to the project. Previous versions of the project were built using .NET Core 1.0 RC1; the changes to the .NET Core project have been drastic and, in most cases, breaking.

EntityFramework Core has a breaking change that affects old installations of the Kraken. If you've installed 1.0.2-prerelease.0 or earlier, you will have to do some manual work to preserve old Release Batches. If you don't mind losing existing data or you have a later version, disregard this and update away!

Fix Migration History

Old releases of Kraken did not specify a max length for string columns, as this was set behind the scenes. New releases need to explicitly state the string length, and if they don't, the length is set to nvarchar(max).

Per ASP.NET's announcement issue you will need to insert a row into Kraken.dbo.__EFMigrationHistory:

INSERT INTO [dbo].[__EFMigrationsHistory] ([MigrationId], [ProductVersion])
VALUES ('20170127195308_Initial', '1.1.0-rtm-22752');

This should "trick" EF into believing the migration history has already been applied, and not lose any existing data.