You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies if an issue isn't the correct venue for this.
I'm working on improving decompiler integration for the Visual Studio debugger. A few months back, @siegfriedpammer kindly reviewed and accepted PR #2678, which I authored as part of my team's effort to support decompilation of binaries built without symbol support. Can you provide any guidance as to when I might see that change in a NuGet package I could consume?
Thanks!
Andrew
The text was updated successfully, but these errors were encountered:
By default, we always have the Actions artifacts (so you can pick a package and add to an internal feed), as well as our https://github.com/icsharpcode/ILSpy/packages/547741 feed (which is GH authenticated if I remember correctly, but that is GH default).
As for nuget.org - that usually happens when we cut a preview / rc / rtm build. That doesn't follow a planned schedule though. @siegfriedpammer might be able to chime in as to when that might be.
Apologies if an issue isn't the correct venue for this.
I'm working on improving decompiler integration for the Visual Studio debugger. A few months back, @siegfriedpammer kindly reviewed and accepted PR #2678, which I authored as part of my team's effort to support decompilation of binaries built without symbol support. Can you provide any guidance as to when I might see that change in a NuGet package I could consume?
Thanks!
Andrew
The text was updated successfully, but these errors were encountered: