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

Improve visibility of Visual Studio extension #1171

Closed
cremor opened this Issue Jun 9, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@cremor
Copy link

cremor commented Jun 9, 2018

Although I'm a long time user of the standalone ILSpy, I just recently learned that there is an Visual Studio extension for it. If I take a detailed look at the GitHub readme, I can find the "VS Extension" button that brings me to the VS marketplace. But the text of the readme, more specifically the "Decompiler Frontends" section, only mentions the VS Code extension. I suggest to also mention the VS extension there.

Although you might want to wait with this change until #1125 (and maybe #1164) is fixed and published to the markedplace, otherwise new users might run into those problems and quickly abandon the extension again.

@christophwille

This comment has been minimized.

Copy link
Member

christophwille commented Jun 11, 2018

Yes, this will have to wait until 3.2 is released as final version.

@dgrunwald

This comment has been minimized.

Copy link
Member

dgrunwald commented Jun 21, 2018

The addin in 3.2 beta is broken again; in a normal (desktop) C# console application, I can't even navigate to the Console.WriteLine in a hello world app.

Edit: I forgot there was a fix to the addin after the beta release. The latest master build from AppVeyor works for my test project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.