denysvuika/il.view

IL.View is an open-source Silverlight .NET assembly browser and decompiler.

il.view's Issues

Export embedded resources

It should be possible to export (save to file) embedded resources.

Source code pane should display source name

Source code pane should display the name of the entity that was disassembled.

Show embedded resources for .NET assemblies

It should be possible to navigate embedded resources for .NET assemblies.

Show embedded resources for Silverlight assemblies

It should be possible to view embedded resources for assembly modules within the Assembly Browser control.

Select next assembly in the list after removal (or enable multiselect)

When an assembly is removed from the list by pressing the Delete key, the first assembly in the list is selected. This makes it impractical to remove assemblies from the middle of the list.
Even better option would be to enable multiselect in the list of assemblies so one could delete all selected assemblies at once.

Provide ready-to-run app package

This is more a continuous task than an issue. The thing is that not everybody who wants to use this tool is able to compile it (for various reasons) so it would be good to provide a package with the ready-to-run app (binaries) with each build/release (or at least the major ones) and make it available for download so one does not need to compile it to use it.

Display .NET/SL Runtime Version for assemblies

Assembly nodes should display .NET/SL Runtime version alonside the assembly name.

Context menus for non-assembly content

Besides a Space bar click there is no other way to display non-assembly content. Context menus should be provided.

Remote assembly repositories

It should be possible to resolve dependencies based on remote repositories (RESTful web services that are able to stream assemblies). The user should be able to configure multiple repository endpoints. Assembly resolution mechanism should allow either locate missing assembly manually or download it from the repository (if the corresponding assembly was found within the repository).

Nuget packages browsing support

Add support for Nuget packages browsing, content preview and/or decompilation.

Images preview for ".xap" packages

It should be possible to preview image files within ".xap" package.

Improve Exeption handling and logging

it should be possible to track error information through Event log;

After handling exeptions of disassemling process application should recovery it's state

Introduce "Help" section

A "Help" section is required with at least basic information towards the tool and its usage.

Reference nodes should be expandable

Reference node should provide information about references for the underlying assembly.
Sample:

• System.Core
  • mscorlib
  • System
    mscorlib

Autosearch missing assemblies

When the app is disassembling and can’t find a dll it will pop up a window where you can click Browse and find the missing dll. I had like 10 missing dlls and even though all of them were in the same folder I got 10 consecutive pop-us and had to search for all of them. Would it be possible to first search for missing dlls in the last browsed folder (or in all previously browsed folders) and if not found then show the popup? It could be an option in the Settings to turn it on/off if someone would like to choose all the missing dlls by himself/herself.

Reference names should contain version info

Reference nodes should contain the version of the corresponding assembly within the node header.
Sample: "System.Windows, Version=2.0.5.0"

Xml files preview for ".xap" packages

Provide possibility to preview xml-based files (xml, xaml, clientconfig, etc.) while browsing ".xap" package.

Re-formatting of xml in case of single-line content.

To improve the readability of xml-based files the content should be re-formatted in case it does not contain line breaks.

Removed assemblies reappear in the list after restart

When I remove .NET assemblies from the list and restart the out-of-browser application the assemblies are back in the list.

In-browser mode support

For the moment application supports only OOB mode. It should be possible to perform the same tasks within browser - no OOB or Full Trust requirements. Expected limitations - no caching of assemblies at local machine, only in-memory caching. Dependencies can be resolved either manually or via remote repositories.

User defined reference paths (full-trust mode)

The end-user should be able to define paths to folders where assemblies should be looked up during "dependency resolution" and decompilation (similar to "Reference Paths" feature in Visual Studio). The application should take user defined paths into account when resolving assembly dependencies (mainly during decompilcation process).

Show file sizes for embedded resource items

It should be efficient to get the sizes of the resource items within the node headers when expanding embedded resource assemblies.

All assembly browser items should expose declaring assembly

In order to aid decompilation and dependency resolution all assembly browser items should procide access to assembly definition particular item belongs to.

Cache ".xap" packages for OOB mode

Silverlight ".xap" packages should be cached for OOB mode and loaded during the next run (similar to assemblies).

Single assembly browser

Assemblies should be loaded into a single list. The header of the assembly should contain some platform identifier (SL, .NET) either in textual or visual way.