#1
|
|||
|
|||
Need an assist with adding locals using DNspy
So I came across a version of .NET Reflector that I believe was manually edited (using DNspy or similar) to remove any and all serial/internet verification checks/etc, thus making the EXE completely portable. I'm trying to backtrack how this was done using an unedited but identical version of the Reflector EXE. I'm 95% there, but I'm stuck on the last bit.
I'm using DNspy, but I cannot figure out how these locals were added: Code:
Reflector.Application.InternalApplicationManager.<>c__DisplayClass0_0__2 Reflector.Application.InternalApplicationManager.<>c__DisplayClass0_1__1 They are showing up under the LOCALS tab of the DNspy dialog that allows you to edit the IL instructions. It's damn frustration because it's the final piece to the puzzle and I can't figure out how to implement these locals into the EXE. A pointer in the right direction would be very helpful. -thx |
#2
|
|||
|
|||
tokens with names like
<>c__DisplayClassXXXXX are for sure generate by the C# compiler Good decompiler transofrts that low-level stuff into high level C# constuctions (eg as ILSpy does) what is the reason to add vars (by hands!?!) that are like internal compiler generated ones? |
The Following User Says Thank You to sendersu For This Useful Post: | ||
niculaita (12-30-2018) |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Dnspy does not hit breakpoint | Turkuaz | General Discussion | 1 | 08-13-2020 01:24 |
dnSpy oddities | LaptoniC | General Discussion | 5 | 05-05-2019 22:34 |
dnSpy Plugins | n00b | Developer Section | 2 | 08-29-2015 17:11 |
RE : Adding mouse functionality | LOUZEW | General Discussion | 7 | 04-26-2005 01:29 |