On September 2nd ASP.NET 5 beta 7 was released. As with beta 6 this release includes a tooling update for Visual Studio. Read the announcement here.
The tooling update can be found here. The relevant files are either DotNetVersionManager-x64.msi or DotNetVersionManager-x86.msi depending on what your system supports and WebToolsExtensionsVS14.msi.
After installing the tooling update change the sdk version in global.json to beta 7.
{ "projects": [ "src", "test" ], "sdk": { "version": "1.0.0-beta7" } }
In the project.js file update beta6 to beta7 in the dependencies section.
"dependencies": { "EntityFramework.SqlServer": "7.0.0-beta7", "EntityFramework.Commands": "7.0.0-beta7", "Microsoft.AspNet.Mvc": "6.0.0-beta7", "Microsoft.AspNet.Mvc.TagHelpers": "6.0.0-beta7", "Microsoft.AspNet.Authentication.Cookies": "1.0.0-beta7", "Microsoft.AspNet.Authentication.Facebook": "1.0.0-beta7", "Microsoft.AspNet.Authentication.Google": "1.0.0-beta7", "Microsoft.AspNet.Authentication.MicrosoftAccount": "1.0.0-beta7", "Microsoft.AspNet.Authentication.Twitter": "1.0.0-beta7", "Microsoft.AspNet.Diagnostics": "1.0.0-beta7", "Microsoft.AspNet.Diagnostics.Entity": "7.0.0-beta7", "Microsoft.AspNet.Identity.EntityFramework": "3.0.0-beta7", "Microsoft.AspNet.Server.IIS": "1.0.0-beta7", "Microsoft.AspNet.Server.WebListener": "1.0.0-beta7", "Microsoft.AspNet.StaticFiles": "1.0.0-beta7", "Microsoft.AspNet.Tooling.Razor": "1.0.0-beta7", "Microsoft.Framework.Configuration.Abstractions": "1.0.0-beta7", "Microsoft.Framework.Configuration.Json": "1.0.0-beta7", "Microsoft.Framework.Configuration.UserSecrets": "1.0.0-beta7", "Microsoft.Framework.Logging": "1.0.0-beta7", "Microsoft.Framework.Logging.Console": "1.0.0-beta7", "Microsoft.Framework.Logging.Debug": "1.0.0-beta7", "Microsoft.VisualStudio.Web.BrowserLink.Loader": "14.0.0-beta7" }
In Startup.cs replace the Microsoft.Framework.Runtime namespace with Microsoft.Dnx.Runtime.
using Microsoft.Dnx.Runtime;
The remaining changes are related to entity framework 7. ApplyMigrations has been change to Migrate.
Before: Database.ApplyMigrations(); After: Database.Migrate();
Any migration designer.cs files will need the following changes. The Microsoft.Data.Entity.Migrations.Infrastructure namespace is now Microsoft.Data.Entity.Infrastructure.
using Microsoft.Data.Entity.Infrastructure;
ContextType has changed to DbContext.
Before: [ContextType(typeof(ContactsDbContext))] After: [DbContext(typeof(ContactsDbContext))]
The ProductVersion property has been removed and BuildTargetModel is now protected.
Before: public override string ProductVersion { get { return "7.0.0-beta6-13815"; } } public override void BuildTargetModel(ModelBuilder builder) After: protected override void BuildTargetModel(ModelBuilder builder)
The Microsoft.Data.Entity.Migrations.Builders namespace is now Microsoft.Data.Entity.Migrations.Operations.Builders.
using Microsoft.Data.Entity.Migrations.Operations.Builders;
Any classes that inherit from the Migration need the Up and Down functions changed to protected.
Before: public override void Up(MigrationBuilder migration) public override void Down(MigrationBuilder migration) After: protected override void Up(MigrationBuilder migration) protected override void Down(MigrationBuilder migration)
The AddCoumn of MigrationBuilder now needs a type specified and nullable has changed to isNullable.
Before: migration.AddColumn(name: "UserId", table: "ContactModel", type: "nvarchar(max)", nullable: true); After: migration.AddColumn<string>(name: "UserId", table: "ContactModel", type: "nvarchar(max)", isNullable: true);
The last change to MigrationBuilder that I ran into was with table.ForeginKey. referencedTable and referencedColumn changed to principleTable and principalColumns.
Before: table.ForeignKey(name: "FK_ContactAddressModel_ContactModel_ContactId", columns: x => x.ContactId, referencedTable: "ContactModel", referencedColumn: "Id"); After: table.ForeignKey(name: "FK_ContactAddressModel_ContactModel_ContactId", columns: x => x.ContactId, principalTable: "ContactModel", principalColumns: new []{"Id"});
That was all the changes needed to get my test project updated. Here is the Github release page and breaking changes page for this release.
Migration of an existing project through the betas does work, but I recommend creating a new project every couple of betas. Things are changing in the project templates as well the core of ASP.NET 5. At the very least create a new project and look through the startup class and implement anything new that you find useful. For example the debug logger is now included when creating a new project.
Thanks for your post!
Just nitpicking; can you fix one block of code with regards to:
>> The AddColumn of MigrationBuilder now needs a type specified and nullable has changed to isNullable.
It should contain the generic signature: AddColumn right?
Carl you are correct. The error has been fixed. Thank you for that catch!
Very helpful. I didn’t realize what a pain using the current code would be!
Glad the post was helpful. Thank you for the comment.