MANY MANY times I have lost carefully crafted assembly lists because: a) the tool auto-loads the previous list, even if you're just launching from VS or Explorer context menu, b) it silently overwrites the list with whatever is loaded in the app when it closes, c) there's no way to control what's in a list, it's just whatever is loaded at the time. I use the list feature a lot, it would be great if it wasn't so automatic - let me setup a list manually and mark it to load all assemblies from one or more folders (recursively), or add assemblies manually from file/gac to the list. have a button to "add currently loaded assemblies into the current list", and please provide a warning if 2 assemblies with the same name are loaded from different locations as 5/7 that's a mistake
in JustDecompile it would be helpful to be able at add referenced assemblies using Nuget, so when either looking at code or exporting code I don't have to do this manually to get the referenced DLL to import into JustDecompile
When clicking a particular recursive function call (go to definition) the entire application hangs and must be reopened.
I think I've whittled the problem down to the following components:
The sequence of events also seems to have a part. After decompiling, select Foo() in the tree to the left, then click the recursive call in the code.
Of course nothing should really happen when this is clicked, as one must be at said definition before clicking the recursive call so nothing would really happen, but still...
For example, select (double click) "Class2016" and close Search dialog, tab content code will Class2016's code, but sometimes the tab texts still "Class1577", no change, please check.
Enable option to generate not only large numbers as hex, but also small numbers (byte, ushort and so on). i mean the numbers in the whole project to be generated a HEX
I am writing some mocks /fakes for code that uses this Logging Framework. So I decompiled the DLL into a project and it would not compile. All I wanted to do was to have some unit tests that can cope with 'Logging'. If your decompile something, if there are problem area, at least a comment would be helpful. Thanks Doug
I don't know why but JD keeps being disassociated with DLLs, and it's a pain to re-associate. Make it easy for us by adding something in settings to do it for us.
It's annoying. Figure out a different way to let us know there's an update.
If a new version of JustDecompile is available, the user will be informed soon after starting the program. At this time the initial intention is getting details of an assembly. I have two options: 1. Ignore update and continue analysis 2. Install update and restart analysis later I want to recommend third option: Allow installation of update after analysis is complete, while shutdown of program. (E.g. Paint.NET is doing so.)