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
Aside from the WPF UI ILSpy (downloadable via Releases, see also plugins), the following other frontends are available:
Visual Studio 2022 ships with decompilation support for F12 enabled by default (using our engine v7.1).
In Visual Studio 2019, you have to manually enable F12 support. Go to Tools / Options / Text Editor / C# / Advanced and check "Enable navigation to decompiled source"
C# for Visual Studio Code ships with decompilation support as well. To enable, activate the setting "Enable Decompilation Support".
Finally, you can manually install the necessary components via the Visual Studio Installer. The workloads/components are as follows:
Workload ".NET Desktop Development". This workload includes the .NET Framework 4.8 SDK and the .NET Framework 4.7.2 targeting pack, as well as the .NET 6.0 SDK and .NET 7.0 SDK (ILSpy.csproj targets .NET 6.0, but we have net472+net70 projects too). Note: The optional components of this workload are not required for ILSpy
Workload "Visual Studio extension development" (ILSpy.sln contains a VS extension project) Note: The optional components of this workload are not required for ILSpy
Individual Component "MSVC v143 - VS 2022 C++ x64/x86 build tools" (or similar)
The VC++ toolset is optional; if present it is used for editbin.exe to modify the stack size used by ILSpy.exe from 1MB to 16MB, because the decompiler makes heavy use of recursion, where small stack sizes lead to problems in very complex methods.
Open ILSpy.sln in Visual Studio.
NuGet package restore will automatically download further dependencies
Run project "ILSpy" for the ILSpy UI
Use the Visual Studio "Test Explorer" to see/run the tests
If you are only interested in a specific subset of ILSpy, you can also use
ILSpy.Wpf.slnf: for the ILSpy WPF frontend
ILSpy.XPlat.slnf: for the cross-platform CLI or PowerShell cmdlets
ILSpy.AddIn.slnf: for the Visual Studio plugin
Note: Visual Studio includes a version of the .NET SDK that is managed by the Visual Studio installer - once you update, it may get upgraded too.
Please note that ILSpy is only compatible with the .NET 6.0 SDK and Visual Studio will refuse to load some projects in the solution (and unit tests will fail).
If this problem occurs, please manually install the .NET 6.0 SDK from here.
Make sure PowerShell is installed (formerly known as PowerShell Core)
Clone the repository using git.
Execute git submodule update --init --recursive to download the ILSpy-Tests submodule (used by some test cases).
Use dotnet build ILSpy.XPlat.slnf to build the non-Windows flavors of ILSpy (.NET Core Global Tool and PowerShell Core).
How to contribute
Report bugs
If you want to contribute a pull request, please add https://github.com/icsharpcode/ILSpy/blob/master/BuildTools/pre-commit to your .git/hooks to prevent checking in code with wrong formatting. We use tabs and not spaces. The build server runs the same script, so any pull requests using wrong formatting will fail.
[tags]c-sharp,decompile,decompiler,decompiler-engine,dotnet,dotnetcore,ilspy,mono,pdb,unity[/tags]
[short_descr]NET Decompiler with support for PDB generation, ReadyToRun, Metadata (&more) - cross-platform!.[/short_descr]
[link] https://github.com/google/gcp_scanner [/link]
[long_descr]
ILSpy
![ILSpy VS extension](https://camo.githubusercontent.com/11dd23b92194e13101d57f587e689bd0ee14daaf835cf66eff35e64e9453c438/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f5653253230457874656e73696f6e2d494c5370792d626c75652e737667)
ILSpy is the open-source .NET assembly browser and decompiler.
Download: latest release | latest CI build (master) | Microsoft Store (RTM versions only)
Decompiler Frontends
Aside from the WPF UI ILSpy (downloadable via Releases, see also plugins), the following other frontends are available:
Features
License
ILSpy is distributed under the MIT License. Please see the About doc for details,
as well as third party notices for included open-source libraries.
How to build
Windows:
git submodule update --init --recursive
to download the ILSpy-Tests submodule (used by some test cases).editbin.exe
to modify the stack size used by ILSpy.exe from 1MB to 16MB, because the decompiler makes heavy use of recursion, where small stack sizes lead to problems in very complex methods.Note: Visual Studio includes a version of the .NET SDK that is managed by the Visual Studio installer - once you update, it may get upgraded too.
Please note that ILSpy is only compatible with the .NET 6.0 SDK and Visual Studio will refuse to load some projects in the solution (and unit tests will fail).
If this problem occurs, please manually install the .NET 6.0 SDK from here.
Unix / Mac:
git submodule update --init --recursive
to download the ILSpy-Tests submodule (used by some test cases).dotnet build ILSpy.XPlat.slnf
to build the non-Windows flavors of ILSpy (.NET Core Global Tool and PowerShell Core).How to contribute
.git/hooks
to prevent checking in code with wrong formatting. We use tabs and not spaces. The build server runs the same script, so any pull requests using wrong formatting will fail.Current and past contributors.
Privacy Policy for ILSpy
ILSpy does not collect any personally identifiable information, nor does it send user files to 3rd party services.
ILSpy does not use any APM (Application Performance Management) service to collect telemetry or metrics.
[/long_descr]
[image] https://raw.githubusercontent.com/gwen001/offsectools_www/main/tmp/21a5f2b7caa8d41929d9f5f22e9655b2.png [/image]
The text was updated successfully, but these errors were encountered: