-
Notifications
You must be signed in to change notification settings - Fork 675
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
Debugger:Unable to resolve 'System.Reflection.Metadata' for '.NETCoreApp.Version=v1.0' #701
Comments
@chuckries @caslan I think we should pull the latest beta release until this is resolved. |
I got this as well. |
I am going to pull the release now. |
OK. If you decide to completely delete the release, go ahead and remove the tag as well. |
The GitHub documentation seems to say that it is possible to delete a release, but it isn't working for me (maybe because I didn't create it?). So I pulled the .vsix and I edited the description so that hopefully it is obvious that the release shouldn't be used. @chuckries do you want to see if you have access to delete it? |
I can delete it. |
Release is removed. Note: the trick is to delete the tag from GitHub, which converts the release to a "draft" release, which can be discarded. |
Sorry everybody, this is my fault. I added the additional nuget feed but didn't want to push the change since it is (hopefully) a temporary workaround. I built the extension locally that works. When I created the release, the CI system built the package for the release page and it did not have my NuGet.config change. I will fix this. |
This has been fixed, the System.Reflection.Metadata we need has been published to nuget.org, no workaround required. |
Environment data
dotnet --info
output:VS Code version: 1.4.0
C# Extension version: v.1.4.0-beta6
.NET Core version: 1.0.0-SDK Preview2
Steps to reproduce
4.Press F5 to start debugging
Expected behavior
The project should be start debugging.
Actual behavior
This project can't start debugging and show some error message in VSCode. Attached as below:
The text was updated successfully, but these errors were encountered: