You are on page 1of 2

10/6/23, 11:17 AM GitHub - icsharpcode/ilspy-vscode: ILSpy Visual Studio Code Extension and Service for Decompiling .

NET Assemblies

icsharpcode / ilspy-vscode Public

ILSpy Visual Studio Code Extension and Service for Decompiling .NET Assemblies

MIT license

114 stars 30 forks Activity

Star Notifications

Code Issues 6 Pull requests 6 Discussions Actions Projects Wiki Security Insigh

master Go to file

dependabot[bot] and Rpinski Bump get-func-name from 2.0.0 to 2.0.2 in /vscode-extension … last week 592

View code

ILSpy Visual Studio Code Extension chat on gitter CI passing Follow @ILSpy

You can install the extension in Visual Studio Code via the marketplace

Getting started
Please see the Getting started overview.

Troubleshooting
If you have issues during installation of .NET Runtime, please see here.

Develop
The extension consists of two parts: The VSCode extension itself (written in TypeScript) and a "backend" server
process (written in C#), which provides a bridge to ILSpy functionality.

If first time

npm i @vscode/vsce -g

Compile and package all parts:

./build vsix

An installable .vsix file should be generated in artifacts folder, if everything is fine.

https://github.com/icsharpcode/ilspy-vscode 1/2
10/6/23, 11:17 AM GitHub - icsharpcode/ilspy-vscode: ILSpy Visual Studio Code Extension and Service for Decompiling .NET Assemblies

Compile only backend server from console:

./build backend

Or open backend/ILSpy-server.sln in Visual Studio 2019 (>= 16.9) or another .NET IDE.

Compile VSCode extension itself:

README.md
./build compile-extension
./build test-extension

To develop and debug the VSCode extension, install Visual Studio Code, then run

cd vscode-extension
code .

Releases

11 tags

Packages

No packages published

Contributors 8

Languages

C# 63.4% TypeScript 26.4% CSS 7.1% PowerShell 1.4% Shell 1.1% JavaScript 0.5% Batchfile 0.1%

https://github.com/icsharpcode/ilspy-vscode 2/2

You might also like