Scott Hanselman

.NET Core 1.0 RC2 - Upgrading from previous versions

May 19, 2016 Comment on this post [24] Posted in ASP.NET
Sponsored By

.NET Core at Core RC2 is out, it's open source, and it's on multiple platforms. I'm particularly proud of the cool vanity domain we got for it. ;) It makes me smile.

Here's the important blog posts to check out:

Head over to and check it out. A great aspect of .NET Core is that everything it does is side-by-side. You can work with it without affecting your existing systems. Be sure also explore the complete .NET Downloads Page for all the manual downloads as well as SHA hashes.

The best way to develop with .NET Core on Windows is to download the Visual Studio official MSI Installer and the latest NuGet Manager extension for Visual Studio. If you don't have Visual Studio already, you can download Visual Studio Community 2015 for free.

We'll have documentation and insights on how to moving from ASP.NET 4.x over to ASP.NET Core 1.0 soon, but for now I've collected these resources for folks who are upgrading from previous versions of .NET Core and ASP.NET Core (the framework formerly new as ASP.NET 5).


Sponsor: Build servers are great at compiling code and running tests, but not so great at deployment. When you find yourself knee-deep in custom scripts trying to make your build server do something it wasn't meant to, give Octopus Deploy a try.

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service
May 19, 2016 23:58
Your "Docker and .NET Core RC2" href is borked... I know because I wanted to check that out :/
May 19, 2016 23:59
Spelling the domain name sounds something like "dot dot net".
May 20, 2016 0:26

Spelling the domain name sounds something like "dot dot net".

Indeed, it's too bad you couldn't have gotten At least then it would have sounded like New York, NY (the city so nice they named it twice)...
May 20, 2016 5:25
Would be nice if there were documentation on how to remove the dnx files from my system since it does not have an installer/uninstaller.
May 20, 2016 7:23

I just spent the night playing with RC2 and trying to get a emptywebsite working in docker with vs code and the command line. It was fun and it feels a little like ruby. Using gulp and yo made me smile. I loved that the template came with a Dockerfile by default.

While trying out Docker, I stumbled across an issue where i couldn't start the webserver on (even though i specified server.urls) instead it was using localhost (which docker doesn't like). I understand that the generators for YO probably haven't been upgraded so i tried to figure this out myself. (My hacky solution (at 2am - i had to figure it out before i went to sleep) was to .UseUrls() in the WebHostBuilder)

The release notes mention that this is infact a breaking change between rc1 and rc2, but doesnt actually explain how to resolve it - ('hosting.json will no longer be read by default.' but nothing to say how to get it read)

It was quite hard to find (mainly because I hadnt turned on Intellisense in VSCode) but the official documentation was a mix of different version and 1/2 complete. (some documents have had a coming soon tag for over 4 months) The best Community blog posts referenced the old releases.

I guess this is still an RC, and I love what is going on with ASP.NET Core. I look forward to RTM when all the documentation is released along side it.


May 20, 2016 11:00
Do I have to migrate my RC1 web app, hosted on Azure App Services, to RC2 or will it continue to function as usual?
May 20, 2016 12:31
Donald Adams,
Remove dnx is a simple as delete the file and shortcut to it.
All you need is remove .dnx folder from you home user directory (cause it's installing per user) and remove it from your "PATH" environment variables (must be users PATH)
May 20, 2016 13:23
The migration guides seem to cover the command-line tools only - is there a migration path for those of us with RC1 projects in Visual Studio? Or is creating a new project based on an RC2 template and manually moving everything over the only way to do it?
May 20, 2016 15:00
I've been looking forward to this.
Small typo "(the framework formerly new as ASP.NET 5)."
should be "(the framework formerly known as ASP.NET 5)."
May 20, 2016 16:16
LoL, sorry Scott, but the domain name wasn't a good choice! :D I agree with Uwe, it's so weird to say out loud and even to read it xD

A good one, in my opinion, would've been! :)
May 20, 2016 18:02
Does .Net Core depend or use dnx? If yes, will the final no longer be tied to dnx?

How does Microsoft recommend hosting .Net Core web apps either today or in the future? It kind of seems like things are moving towards containers (i.e. Docker) instead of your traditional IIS.
May 20, 2016 19:36 is great

For migrating from 4.6.1, I found this:

Curious to learn if the API Port OSS tool is ready for RC2.
May 21, 2016 1:33
I have a server that is not connected to internet. I created offline package using /layout option but get an error 0x80070001 when I run the package. How can I create a bug report?
May 22, 2016 0:06
Reading posts I wonder why people are using RC1 OR RC2 to develop production stuff with it.

RC2 is just not ready and RC1 was of course not.

MS vision is terrible at times but quality on products is pretty good.

People please wait for the final release or your production stuff. It will safe you're hair from turning gray.

May 23, 2016 5:41
Ruslan Khasanbaev,

Thank you. I removed .dnx from user path and removed the folder.

How about: C:\Program Files\Microsoft DNX and it's inclusion in the system path variable.

Can I remove it too?
May 23, 2016 14:18
Donald Adams,
hmm... I didn't notice this folder (in linux dnvm also located in /hove/<user>/.dnx), yes I believe you can remove it too and clear the system Path envVar too (just to save more free space in PATH var for future, cause Windows still have only 2048 chars for any paths).
May 23, 2016 23:25
If you were <a "">Exploring the new .NET "dotnet" Command Line Interface (CLI)</a> make sure you uninstall any previous version of it before making your first experiments with .NET Core 1.0 RC2.

It took me hours to find out why Visual Studio is complaining about the project being configured for soemthing ...rc1 and failing to build the freshly created solution afterwards.

Perhaps this might be worth mentioning next to "Remove all previous versions of .NET Core from your system by using Add/Remove programs." at

Like "Also make sure that you remove all previous versions of the .NET dotnet CLI".
May 24, 2016 1:34
So confusing... 3 official Microsoft blogs, and all inconsistent in how they describe the products. Add the multitude of GitHub repositories being abused to function as 'homepages' for different parts of the stack, and it's incredible anyone would understand what it is they're installing.

When are you guy going to get your act together? Can you please do a stand up on this fubar?
May 24, 2016 13:25
There is no guidance on migration class libraries of web application. Has any one has some guidance for that.
May 25, 2016 17:06
.NET Core RC2 is update is good news. The best thing that I like is that it can work side-by-side without affecting your existing systems. This was something most users will feel relived to know. Thanks for the update.
June 14, 2016 7:28
Amazing info and i really like your work! thanks a lot or sharing! Free Android APK file download safe link apkdom best safe APK downloader free download mirror xapk obb server CoC private link. Love fun ideas lovematchfun join now. The Best Prank Apps, jokes and shocking Games for Android. prankyapps electric screen joke, Love Match test Prank, transparent screen android app, etc. Free Android app APK download softlot app games APK downloader. Gift Ideas giftspilot gifts for her and kids.
So, yes, ads are coming to Wholesale Jerseys 2016 uniforms. Maybe not next year, but soon, and for the rest of our viewing lives. At least we can take heart in the fact that we won't be watching, say, the Citibank Giants play the Coca-Cola Falcons. Yet.
One key, of course, is matching the right sponsor with the right team. The NFL will have its say in advertiser selection Kansas City Chiefs Jersey , to avoid some Texas offramp strip club sponsoring the Cowboys or some Bay-area pawn shop hooking up with the Raiders. You'll be looking at multi-year agreements; this won't be like NASCAR, where advertisers can switch from week to week and certain unfortunate cars might run without ads at all Pittsburgh Steelers Jersey . Dozens of companies are willing to spend millions for 30 seconds of Super Bowl ad time; you think there won't be a line out the door to buy three hours' worth?
June 17, 2016 10:56

Thanks a lot for sharing these links dude !! We get to know all the best Software company in India thru ur amazing blog.Cheers !!

Thanks Regards!
June 17, 2016 23:00
Here's the funny thing...

When classic asp first came out in 1996, developers in the Microsoft ecosystem were ecstatic. It allowed Microsoft developers to more easily develop web applications than the existing methods (i.e. ISAPI extensions or CGI applications)

When ASP.Net first came out in 2002, Microsoft developers were excited to get a new set of tools that got us away from the spaghetti-code that complicated web applications had become. It also introduced a robust framework that allowed us to focus on developing our application rather than the plumbing underneath.

In 2008, I was at PDC in LA, and attended several seminars on the new framework Microsoft was working on called MVC. I didn't know much about it at the time, but it was Microsoft's newest framework, and they were pushing it hard. With my past experience, I was very interested in finding out more about it. A funny thing happened, though. I was underwhelmed. It didn't give me any new capabilities (other than maybe developing simple CRUD applications). Sure, it allowed for "separation of concerns", but a good developer can do this in most languages and a bad developer can create spaghetti in almost any language.

During this same time, Microsoft also started the ongoing process of killing VB.Net without actually discontinuing it. I read the writing on the wall with that one and made the migration to C#. Similar to MVC, however, there was no productivity gained from the move (even after the learning curve).

Fast forward to 2016. Microsoft is creating their first major directional change in 8 years. It's hard to tell what the advantages are with all the hype, but it seems to boil down to:

  • Open Source (who cares?)

  • Can be run on multiple operating systems (yawn...)

  • Less functionality on initial release (wtf?)

What they will be killing off is:

  • Web Forms

  • VB.Net

  • Half of the .Net Framework

Now before the trolls come on and accuse me of being a Luddite, I have traditionally been an early adopter of new technologies. However, this time, I'm going to take a pass. I have a feeling ASP.Net MVC Core Version 1.0 (or whatever the final name happens to be) is going to be a dead branch on Microsoft's technology tree within 3-5 years. The problems it is designed to solve do not seem remotely worth the headaches it is going to cause.

You can have two of the three: Open Source, Extensive Functionality, or "It Just Works". In this case, Microsoft seems to have decided to just pick one (and the least important of the three). Until Microsoft kicks the open source zealots out of the temple, they won't be able to write quality software that solves actual problems. Hopefully, this soon-to-be fiasco does the trick.

Based upon the icy reception and lack of enthusiasm from the developer community, it just might.
July 15, 2016 9:20
It's really very nice update on core. Yes you are write it is the important blog post. I read this and got idea about the great aspect of .NET Core. If you want to get more knowledge about ASP.NET you can visit

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.