ASP.NET Core 1.0 RTM was announced on 27th-Jun-2016, just after a couple of days of RC2 announcement. And if you have migrated your application to RC2 from RC1, then now it’s time to migrate it to RTM from RC2. Find a quick migration guide for ASP.NET Core RTM from RC2.
Migration guide for ASP.NET Core RTM from RC2
Installation
Please remove previous installation of,
- Preview Tooling Preview 1
- .NET Core Runtime SDK (all versions)
- .NET Core Runtime (all Versions)
And now download the new installers and install it.
- Visual Studio Update 3
- Download the .NET Core installer based on platform and architecture of your system from here. On that page, you will find a list of various downloads for each platform.
You probably only need to download one of these:- .NET Core = Run apps with .NET Core runtime.
- .NET Core SDK = Develop apps with .NET Core and the SDK+CLI (Software Development Kit/Command Line Interface) tools.
- And finally, Tooling Preview 2
So now you can open your RC2 application in VS 2015 but RC2 project.json needs to be migrated as well.
Project.json changes
- Find “rc2-final” in project.json and replace it with empty string. So “1.0.0-rc2-final” should be “1.0.0”.
- Rename all 1.0.0-rc2-* to 1.0.0 too. You need to do it for
Microsoft.NETCore.App
- And since the tooling version is also changed now. So rename all the preview 1 bits to preview 2 (1.0.0-preview1-final –> 1.0.0-preview2-final)
- There is no need to use
imports
in project.json. So,{ "tools": { "Microsoft.AspNetCore.Server.IISIntegration.Tools": { "version": "1.0.0-preview1-final", "imports": "portable-net45+win8+dnxcore50" } } }
becomes,
{ "tools": { "Microsoft.AspNetCore.Server.IISIntegration.Tools": "1.0.0-preview2-final" } }
Also read this post to find out project.json changes with ASP.NET Core RC2 release. BTW, just to let you know that Project.json for ASP.NET Core is going away
You may encounter small issues (please put it in comments section) but my sample RC2 application was running successfully on ASP.NET Core RTM after following above migrations point.
Happy converting..
Summary
The migration is straight forward and easy. And the good thing is that there are no code breaking changes also. Thank you for reading and I hope it helped you. Keep visiting this blog and share this in your network. Please put your thoughts and feedback in comments section.