-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
dotnet store fails with error that it cannot find DiaSymReader #8347
Comments
@eerhardt: Eric, could you please take a look? |
The default experience for To unblock yourself you can either:
We should investigate how to get the correct Microsoft.DiaSymReader.Native during |
Related: aspnet/MetaPackages#135 |
Should we revert this until this is resolved? It's really disruptive when changes like this come down the pipe and break something that's been working for months. |
Does one of the two above workarounds not work for you until this is fixed? If they don't work for you, we can back the change out. But it would be more work, adding more risk and time to the 2.0 release. |
I'm testing this out and running into some issues. Currently trying to figure out if they are related to the store or something else. |
I have a fix for this issue I am testing out locally. So it hopefully shouldn't be too long... |
@eerhardt - what I'm seeing now is that I can create the store, but I fail consistently at runtime with:
Notice it's not probing my store for the reference assembly. Is this a separate issue?
|
It looks like a separate issue that was fixed a few weeks ago. https://github.com/dotnet/core-setup/issues/2496. Is there anyway you can check which version of Microsoft.Extensions.DependencyModel is being referenced by that app? Try looking in the .deps.json file or the project.assets.json file. Which version of ASP.NET are you referencing? |
This is happening for me with the 2.0.0-preview1 release of ASP.NET and the newest shared framework/SDK The version of dependency model in my project.assets.json is 2.0.0-preview1-002111 |
Yep, that's the issue. After preview1, there was a request to remove the ASP.NET assemblies from the Basically, the newer SDK is not compatible with the ASP.NET preview1 runtime out of the box, since it no longer copies files the preview1 runtime needed. An easy way to work around this issue is to add Other options would be:
|
OK interesting, I'm not sure why we're just running into this now. I'll try hoisting dependency model |
Thanks @eerhardt - hoisting the dependency model workaround that issue, so it looks like we're not blocked here. |
I believe this issue has been fixed now that we inserted an SDK with the fix in the CLI. |
To fix this, copy crossgen to the netcoreapp folder that has DiaSymReader in it, and invoke crossgen from there. Fix #6778
Steps to reproduce
The complete scenario is here: https://github.com/aspnet/JitBench/blob/dev/README.md
This has been working for a while and regressed in the past few days.
The issue is when the store is generated by this script:
.\AspNet-GenerateStore.ps1 -InstallDir .store -Architecture x64 -Runtime win7-x64
This is the command that is run by the script:
Expected behavior
Dotnet store runs successfully
Actual behavior
Crossgen fails on generating pdb with error
Environment data
dotnet --info
output:CC @lt72 @rynowak
The text was updated successfully, but these errors were encountered: