Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FileLoadException on System.Runtime with FrameworkReference #638

Closed
sebastienros opened this issue Dec 6, 2019 · 11 comments
Closed

FileLoadException on System.Runtime with FrameworkReference #638

sebastienros opened this issue Dec 6, 2019 · 11 comments
Labels
area-Infrastructure untriaged New issue has not been triaged by the area owner

Comments

@sebastienros
Copy link
Member

I am hitting an issue that I filed on the sdk repos here: dotnet/sdk#3929
It contains all the details and a repro app, but I think it's related to corehost.

@dagood dagood transferred this issue from dotnet/core-setup Dec 6, 2019
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added area-System.Runtime untriaged New issue has not been triaged by the area owner labels Dec 6, 2019
@jkotas
Copy link
Member

jkotas commented Dec 7, 2019

System.Runtime.dll is version 4.2.1.0, but the PlatformBenchmarks.dll is referencing 5.0.0.0. I guess this is problem with build coherency:libraries implementations are from before the 5.0 version bump, but everything else is from after the 5.0 version bump.

@jkotas
Copy link
Member

jkotas commented Dec 7, 2019

This should fix itself on its own once dotnet/runtime start flowing through the system.

@joshpearce
Copy link

joshpearce commented Dec 10, 2019

This should fix itself on its own once dotnet/runtime start flowing through the system.

To see that eventual fix, do I just need to keep pulling the latest from the AspNetCore repo, building, activating the custom environment, creating a new project and trying to run it? Is there anything specific I can be on the lookout for to know that the runtime has "flowed through the system"?

@jkotas
Copy link
Member

jkotas commented Dec 10, 2019

@dotnet/runtime-infrastructure What is the current ETA for having live-live official builds from the consolidated runtime repo?

@trylek
Copy link
Member

trylek commented Dec 10, 2019

End of this week or early next week assuming there are no further AzDO hiccups, otherwise I doubt we can get to them before the New Year with the oncoming EOY holidays.

@jkotas
Copy link
Member

jkotas commented Dec 10, 2019

@trylek Is there issue tracking the live-live official build that people can watch?

@safern
Copy link
Member

safern commented Dec 10, 2019

That would be: #98

@trylek
Copy link
Member

trylek commented Dec 10, 2019

Great, thanks Santi for sharing. Internally this is tracked under the work item

https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1020770

currently assigned to me.

@sebastienros
Copy link
Member Author

What "build" should I follow? There is a dotnet/core-sdk and dotnet/sdk. It looks like I'd need to use dotnet/sdk but the latest built version mentioned doesn't work with dotnet-install.

@dagood
Copy link
Member

dagood commented Jan 10, 2020

I've been posting some updates about the dotnet/runtime official build at #98. At the moment dotnet/toolset and dotnet/extensions uptake is blocked, but that should be fixed soon (#1129).

Once that flows through, the SDK zips that redist the various runtimes (what dotnet-install downloads) are built by dotnet/core-sdk, so you'll need to look for a build there.

But if you don't need a full SDK zip, just the .NET Core Runtime to try out with your repro app, those are already available. Unfortunately you need to make the URL yourself until we get an Arcade feature to let us make the dotnet/runtime readme work. (Some context on that: #1154 (comment).)

@sebastienros
Copy link
Member Author

Fixed, thanks

@ghost ghost locked as resolved and limited conversation to collaborators Dec 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure untriaged New issue has not been triaged by the area owner
Projects
None yet
Development

No branches or pull requests

7 participants