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
Hi all, I was wondering if maintainers are open to returning Node values in response to certain commands. I'd really like to integrate my vscode extension with ilspy-vscode. Let me know, I'd be open to implementing, too.
For context, an extension can decompile an assembly by calling decompileSelectedAssembly, but doesn't get anything back in terms of symbol tokens. If that extension wanted to subsequently open the decompiled assembly in a new tab, they'd need the info from a Node to construct an ilspy:// uri.
The text was updated successfully, but these errors were encountered:
Hi James, it should be easy to return the Node object of added assembly. Then you could use the "decompileNode" command to open its code in a new editor etc.
Awesome @Rpinski much appreciated! I'd love to see a getAllNodes command too if that's something you see worthwhile for the project. The use case would be to get il state post extension restart. Let me know, I'm also open to doing that
Hi all, I was wondering if maintainers are open to returning Node values in response to certain commands. I'd really like to integrate my vscode extension with ilspy-vscode. Let me know, I'd be open to implementing, too.
For context, an extension can decompile an assembly by calling decompileSelectedAssembly, but doesn't get anything back in terms of symbol tokens. If that extension wanted to subsequently open the decompiled assembly in a new tab, they'd need the info from a Node to construct an ilspy:// uri.
The text was updated successfully, but these errors were encountered: