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
When you load and decompile an assembly, dnSpy will try to load most of the dependencies the assembly needs. However, this clogs up the tree very quickly when multiple assemblies are loaded at once.
Proposal
It would be nice to have a feature where, similar to the Remove Assembly(ies) option, we have a Hide Assembly(ies) option that simply hides the assemblies from the tree. Normally one wouldn't be looking through those anyways for the most part.
Alternatives
One another idea I came to regarding this is that there could also be a filtering system. One could tag certain assemblies, with No Tag and Hidden being default ones. The user can create custom ones (eg. Microsoft or Unity) as they see fit and tag assemblies as such in the context menu.
Additional Context
Just a simple way to showcase the problem, I had removed all assemblies and loaded the Assembly-C-Sharp.dll file for the unity game Slime Rancher.
I just want to see the first assembly, the others should either be automatically hidden or left up to the user (latter is preferred).
The text was updated successfully, but these errors were encountered:
Problem Description
When you load and decompile an assembly, dnSpy will try to load most of the dependencies the assembly needs. However, this clogs up the tree very quickly when multiple assemblies are loaded at once.
Proposal
It would be nice to have a feature where, similar to the
Remove Assembly(ies)
option, we have aHide Assembly(ies)
option that simply hides the assemblies from the tree. Normally one wouldn't be looking through those anyways for the most part.Alternatives
One another idea I came to regarding this is that there could also be a filtering system. One could tag certain assemblies, with
No Tag
andHidden
being default ones. The user can create custom ones (eg.Microsoft
orUnity
) as they see fit and tag assemblies as such in the context menu.Additional Context
Just a simple way to showcase the problem, I had removed all assemblies and loaded the

Assembly-C-Sharp.dll
file for the unity game Slime Rancher.I just want to see the first assembly, the others should either be automatically hidden or left up to the user (latter is preferred).
The text was updated successfully, but these errors were encountered: