Decompiling .net assembly with dotPeek gives invalid syntax

Question

I have a problem with decompiling .net assembly. When I open the assembly in dotPeek there is class called frmMain with few hundred variables declared like this:

[SpecialName]
private static int \u0024STATIC\u0024SortByLengthAsc\u002402811241124\u0024xlen;

When i try to export it to project all those lines give errors (STATIC is not defined) even if I change all the \u0024 to $. Am I doing something wrong?

Patrick Hofman · Accepted Answer · 2016-11-03T15:50:52.470

3

No, the assembly has been obfuscated to prevent people (like you) to take a peek in the code and possibly 'steal' it. Those variable names are allowed in IL, but not in actual C# code, so that is why it fails.

The only remedy I know is a reverse-obfuscation tool that knows how the obfuscator obfuscates and tries to turn that around. Or you can do it by hand, which will take a lot of time usually, which proves obfuscation pays off.

edited Nov 03 '16 at 15:50

answered Nov 03 '16 at 15:49

Patrick Hofman

153,850
22
249
325

The author of the obfuscation package probably has another product that deobfuscates obfuscated code for debug purposes – Panagiotis Kanavos Nov 03 '16 at 15:50
Usually that is true @PanagiotisKanavos – Patrick Hofman Nov 03 '16 at 15:52
I will just ask my friend (author of that program) to give me the source code than. Thanks for answer – Jan Polak Nov 03 '16 at 15:55
I am seeing similar output after decompiling Microsoft .NET Framework assemblies such as PresentationFramework.dll. I thought those assemblies are not obfuscated, as they are now open source? – Sabuncu Feb 12 '19 at 17:49

score 1 · Answer 2 · answered Aug 21 '22 at 17:43

1

Quick tip for anyone got this question in Google: Try ILSpy (for example) instead of dotPeek.

Got this unicode stuff with dotPeek in a non obfuscated dll, but everything is fine with ILSpy

answered Aug 21 '22 at 17:43

Gleb S

152
2
13

Decompiling .net assembly with dotPeek gives invalid syntax

2 Answers2

Linked