ASP. 5 Adventure (6): Upgrade ASP. 5 to Beta6

(This article also published in my public number "dotnet daily Essence article", Welcome to the right QR code to pay attention to. )

Preface: Microsoft released the BETA6 as scheduled on the ASP. NET 5 Roadmap, and now we're talking about beta5 upgrading to BETA6.

Previously, Microsoft unveiled the Roadmap for ASP. Https://github.com/aspnet/home/wiki/roadmap. NET 5. According to the Roadmap, an ASP. 5 Beta6 was released on July 27. Since Microsoft was released on July 20 for Visual Studio RTM (built-in ASP. NET 5 beta5), BETA6 still needs to install it manually. In order to wait for the installation of Windows 10 on July 30 before installing visual Studio RTM, the project code was upgraded to BETA6 yesterday.

Upgrade the Beta5 Beta6 Although the previous method can also be used (public number reply: 20150707), but given that VS2015 has RTM, Microsoft has provided us with an installation package for the upgrade, which is downloaded here (http://go.microsoft.com/ fwlink/? linkid=619565). One of the installation packages is for installing DNVM (divided into x64 and x86) and one for installing the runtime (in different languages).

After upgrading the DNVM and Dnx runtimes, the only thing to do is to change the BETA6 (https://github.com/aspnet/Announcements/issues?q=is%3Aopen+is%3Aissue+ MILESTONE%3A1.0.0-BETA6) resolves the compile and run issues that occur with the code. Here is a brief description of some of the problems I encountered with my project code:

The functionality of the
• MVC is broken down into more granular packages that facilitate smaller additions and dependencies. For example, Viewcontext,viewcontextattribute and Ihtmlhelper are moved to Microsoft.AspNet.Mvc.ViewFeatures
• The format of the Project.lock.json file changes and is eventually fixed, so you need to re-execute the dnu restore
• Builder. Forsqlserver (). Useidentity (); Use builder instead. Usesqlserveridentitycolumns ();
• Entityoptionsbuilder instead of Dbcontextoptionsbuilder
• Microsoft.dataannotations was discarded (in fact, I gave up in Beta4, I was quoted before), now do not use Indexattribute, but instead of using FLUENTAPI to define the index, more instructions see (https:// github.com/aspnet/entityframework/issues/1698)
• MICROSOFT.FRAMEWORK.CODEGENERATORS.MVC does not have a beta6 version, but does not seem to be interfering with
• isessioncollection instead of ISession
• SignIn use signinasync,signout instead of Signoutasync
• useinmemorysession instead of usesession
• errorpageoptions.show All obsolete
• calling the database initialization code in Starup needs to be changed, see my issue report on GitHub (https://github.com/aspnet/Identity/issues/529)
• as a foreign key property, if it is a string to explicitly define the length of the string (previously can be set automatically according to the primary key)
The scaffolding of the
• Beta6 (that is, the default project code structure) has changed, mainly involving the front end package Reference Bower Section

These are some of the experiences of upgrading BETA6.

ASP. 5 Adventure (6): Upgrade ASP. 5 to Beta6