Skip to content
.NET Decompiler
C# Other
  1. C# 99.8%
  2. Other 0.2%
Branch: master
Clone or download
siegfriedpammer Merge pull request #1801 from icsharpcode/avalondock
Second iteration of docking UI for ILSpy
Latest commit 7e34413 Nov 17, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
AvalonDock @ e5ec95d Add AvalonDock as submodule for the time being. Nov 16, 2019
BuildTools Fix update-assemblyinfo.ps1 for worktrees Nov 16, 2019
ICSharpCode.Decompiler.Console Merge pull request #1740 from icsharpcode/issue1677 Oct 22, 2019
ICSharpCode.Decompiler.PdbProvider.Cecil See #1416. Also upgraded Cecil to .3 (from .1) Feb 14, 2019
ICSharpCode.Decompiler.PowerShell Add LanguageVersion, RemoveDeadCode and RemoveDeadStores options to p… Oct 2, 2019
ICSharpCode.Decompiler.Tests Adjust async-streams decompiler for dotnet/roslyn#39436 Nov 10, 2019
ICSharpCode.Decompiler Merge pull request #1791 from icsharpcode/issue1749-part3 Nov 10, 2019
ILSpy-tests @ aa8f119 Update ILSpy-tests Jul 30, 2019
ILSpy.AddIn Ancsestor -> Ancestor Oct 13, 2019
ILSpy.BamlDecompiler.Tests Switch to net472, of note: Sep 2, 2019
ILSpy.BamlDecompiler Update to latest MEF NuGet packages Sep 28, 2019
ILSpy.Package Back to neutral for package, Any CPU for build Sep 9, 2019
ILSpy.Tests Adjust async-streams decompiler for dotnet/roslyn#39436 Nov 10, 2019
ILSpy Update Resources used in new panels + code cleanup. Nov 17, 2019
SharpTreeView commiting -> committing Oct 13, 2019
TestPlugin Switch to net472, of note: Sep 2, 2019
doc Update copyright year Jan 2, 2019
.editorconfig Add YAML settings to editorconfig. Must use spaces Jun 4, 2019
.gitattributes Add .gitattributes and normalize newlines Oct 1, 2013
.gitignore Exclude wapproj generated directories Jun 5, 2019
.gitmodules Add AvalonDock as submodule for the time being. Nov 16, 2019
.tgitconfig Add tgit.icon project config Apr 6, 2014
DecompilerNuGetDemos.workbook Update frontends for 5.0 RTM Sep 19, 2019
Frontends.sln Try switching .Decompiler.Console on Release(NuGet)/Debug(ProjectRef)… Oct 2, 2019
ILSpy.WithPackage.sln Bundle for x86 & x64 only, remove ARM targets Sep 9, 2019
ILSpy.sln Add AvalonDock as submodule for the time being. Nov 16, 2019
NuGet.config Add first attempt at PdbGenerationTestRunner. Feb 16, 2019
README.md Update README.md Oct 23, 2019
appveyor.yml Merge branch '5.0.x' of https://github.com/icsharpcode/ILSpy Sep 27, 2019
azure-pipelines.yml Apply fix as per #1748 (comment) Nov 11, 2019
clean.bat #1598: Fix .bat files to use VS2019. Aug 5, 2019
debugbuild.bat #1598: Fix .bat files to use VS2019. Aug 5, 2019
global.json Remove old hacks for decompiler csproj Sep 29, 2019
preparerelease.bat #1598: Fix .bat files to use VS2019. Aug 5, 2019
releasebuild.bat #1598: Fix .bat files to use VS2019. Aug 5, 2019

README.md

ILSpy Join the chat at https://gitter.im/icsharpcode/ILSpy NuGet Build status Twitter Follow ILSpy VS extension Build Status

ILSpy is the open-source .NET assembly browser and decompiler.

Download: latest release | latest CI build (master) | Microsoft Store (RC & RTM versions only)

CI Build Nuget Feed (master): https://ci.appveyor.com/nuget/ilspy-masterfeed

Decompiler Frontends

Aside from the WPF UI ILSpy (downloadable via Releases, see also plugins), the following other frontends are available:

Features

  • Decompilation to C#
  • Whole-project decompilation (csproj, not sln!)
  • Search for types/methods/properties (substring)
  • Hyperlink-based type/method/property navigation
  • Base/Derived types navigation, history
  • BAML to XAML decompiler
  • Extensible via plugins (MEF)
  • Check out the language support status

License

ILSpy is distributed under the MIT License.

Included open-source libraries:

  • Mono.Cecil: MIT License (part of ILSpy)
  • LightJson: MIT License (part of ICSharpCode.Decompiler)
  • Humanizer: MIT License (part of ICSharpCode.Decompiler)
  • AvalonEdit: MIT License
  • SharpTreeView: LGPL
  • ILSpy.BamlDecompiler: MIT license
  • CommandLineUtils: Apache License 2.0 (part of ICSharpCode.Decompiler.Console)

How to build

Windows:

  • Install Visual Studio (documented version: 16.3) with the following components:
    • Workload ".NET Desktop Development". This includes by default .NET Framework 4.8 SDK and the .NET Framework 4.7.2 targeting pack, as well as the .NET Core 3.0 SDK (ILSpy.csproj targets .NET 4.7.2, and ILSpy.sln uses SDK-style projects).
    • Workload "Visual Studio extension development" (ILSpy.sln contains a VS extension project)
    • Individual Component "MSVC v142 - VS 2019 C++ x64/x86 build tools (v14.23)" (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.
  • Check out the ILSpy repository using git.
  • Execute git submodule update --init --recursive to download the ILSpy-Tests submodule (used by some test cases).
  • 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

Note: Visual Studio 16.3 and later include a version of the .NET Core SDK that is managed by the Visual Studio installer, once you update to 16.4 it may get upgraded to version 3.1. Please note that ILSpy is not compatible with the .NET Core 3.1 SDK and Visual Studio will refuse to load some projects in the solution. If this problem occurs, please manually install the .NET Core 3.0 SDK from here.

Unix / Mac:

  • Make sure .NET Core 2.1 LTS Runtime is installed (you can get it here: https://get.dot.net).
  • Make sure .NET Core 3.0 SDK is installed.
  • Check out the repository using git.
  • Execute git submodule update --init --recursive to download the ILSpy-Tests submodule (used by some test cases).
  • Use dotnet build Frontends.sln to build the non-Windows flavors of ILSpy (.NET Core Global Tool and PowerShell Core).

How to contribute

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.

You can’t perform that action at this time.