Accelerate decompilation process (to get usings only) #2977
-
|
Hi, I would like to ask you, if there's an option to accelerate decompilation process to get usings only, please? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 11 replies
-
|
Usings depend on whether the decompiler had to introduce temporary variables (in which case it'll spell out the variable type which might need a using), or could simplify the logic into a single expression (in which case the type of the temporary doesn't need a using). |
Beta Was this translation helpful? Give feedback.
-
|
The scanner is based on scanning for suspicious (reported) nugets, that's why I am interested in usings /references/, for this task full decompilation is "more accurate", right? I am not interested in class level analysis, this has to be done manually afterwards as it's not easy to do. |
Beta Was this translation helpful? Give feedback.
-
|
Wouldn't looking for references be sufficient? Or do you have the problem of transitive references? |
Beta Was this translation helpful? Give feedback.
-
|
I find working with usings more reliable, as it's required for existing code, references are tricky - can be unused, have dependencies, ... Correct me, if I am wrong, please. Anyway is there a way how to get references, please? |
Beta Was this translation helpful? Give feedback.
-
|
AFAIK the C# compiler already ignores unused references (doesn't store them in the .dll), so if you don't want class-level analysis, references from the .dll should be good enough. (though note that references use assembly-granularity, where as usings are namespace-granularity) |
Beta Was this translation helpful? Give feedback.
-
|
@dgrunwald, thank you for GREAT advice, it's lightning FAST! |
Beta Was this translation helpful? Give feedback.
AFAIK the C# compiler already ignores unused references (doesn't store them in the .dll), so if you don't want class-level analysis, references from the .dll should be good enough. (though note that references use assembly-granularity, where as usings are namespace-granularity)
You don't need a decompiler at all in that case; you can e.g. directly use System.Reflection.Metadata, or maybe Mono.Cecil as that tends to be easier to use.