Runtime error (System.Runtime 4.2.0.0 not found) using nightlies

As per https://github.com/dotnet/cli/issues/5242 - have narrowed down my issue to the EF Core preview1 packages.

Exception when using dotnet run is as follows:

Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System.Runtime, Version=4.2.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

If there’s some guidance, notes or announcement I missed would you mind pointing me to it? Have been happily running nightlies until I pushed a new build of my app to Azure a few days ago, whereupon some new version caused this issue for me.

Further technical details

EF Core version: Remind me how to do this for VS2017 please? There is no packages.config or project.json. is there a lock file? Database Provider: Microsoft.EntityFrameworkCore.SqlServer Operating system: Win 10 IDE: Commandline … but also VS2017

[muratg]

@kierenj, in case you’re interested in “standalone” (AKA self-contained apps):

• For project.json based projects, Scott Hanselman has a blog post: http://www.hanselman.com/blog/SelfcontainedNETCoreApplications.aspx
• For csproj projects: https://docs.microsoft.com/en-us/dotnet/articles/core/preview3/deploying/

[muratg]

So I feel that a working version and running on an App service are mutually exclusive.

@muratg Are you familiar with this? Any thoughts?

I would phrase it differently: nightly builds of the SDK and the runtime are not deployed to Azure App Service. Azure App Service is updated only when there’s a public release.

If you’d like to still deploy with nightlies, you can build your app as a “standalone” app, i.e. packing and deploying the runtime itself with your app. Just a reminder though, only public RTM releases are considered “officially supported”.