Visual Studio Hacks

Obfuscate Your Code #80

Chapter 10, Work with Visual Studio Tools

|

349

HACK

3. Click the Trigger tab and notice that nothing is there. Now click

Browse, search for your assembly, and click Open. You’ll see that your

assembly has been added to the Dotfuscator Project.

4. Click the Build tab. For the Destination Directory, click Browse, search

for the directory where you want to place the obfuscated assembly, and

click OK. Be sure this directory is not the same directory where the

Debug assembly is placed.

5. Click File

➝ Save Project (Ctrl-S). Browse to the location where you

want the XML file saved, give it a name, and click Save.

Build the Dotfuscator Project

Now that you’ve created and saved a Dotfuscator Project, you can build it.

Click File

➝ Build (Ctrl-B). This will rebuild your assembly with the obfus-

cation options you specified in the Dotfuscator Project.

Now that you’ve got an obfuscated assembly, let’s take a look at it using two

well-known tools, ILDASM and Reflector.

Investigate the Results with ILDASM

As you know, ILDASM can be used to view an assembly's manifest and its

IL code

[Hack #63]. You can use this tool to verify the Dotfuscator did its job by

Figure 10-25. Dotfuscator window

350

|

Chapter 10, Work with Visual Studio Tools

#80 Obfuscate Your Code

HACK

comparing the obfuscated assembly ...