Updating from ASP.NET Core 1.1.1 to 1.1.2 requires host upgrade?

[nvivo]

This is more of a question than an issue, but I haven't found an answer anywhere and SO didn't seem the right place for it.

I remember the talks saying .net core would allow simpler upgrades to the app without requiring server changes because all dependencies are in the app folder.

It just happened that I upgraded a very simple website (no dependencies other than the framework) from ASP.NET Core 1.1.1 to 1.1.2 and I wasn't able to make the app run without reinstalling the hosting component to the new version on Windows Server. In fact, every new minor version of ASP.NET Core required an upgrade to the server as far as I can remember.

So first, should a patch version require a server component upgrade?
And second, are we always going to require a host upgrade to update asp.net core apps or is this a temporary thing?

[martincostello]

I had a similar experience, and it was because I hadn't pinned my runtime version in the project, meaning that when I recompiled after updating to MVC 1.1.3, it compiled against the 1.1.2 runtime as it was the latest one on my machine. Azure App Service hadn't yet been updated with the new runtime yet at that point, so my site failed to start up when the updated version was published.

I resolved it by setting the RuntimeFrameworkVersion property (see under Recommendations in the docs) in the csproj file to 1.1.1 until the new runtime was available in Azure.

[mkArtakMSFT]

Yes, there is a server component installer which is required for this.