Phil Leggetter - Software Consultant

As I was cleaning up the contents of my desktop I came across a text file containing a list of links to .NET obfuscator offerings. I created this list when researching options about six months ago. The main criteria was that the obfuscator could be executed as part of an automated build process.

Here’s the contents of the list:

• http://www.remotesoft.com/salamander/obfuscator.html
• http://www.smartassembly.com/
• http://www.preemptive.com/products/dotfuscator/index.html
• http://www.9rays.net/products/Spices.Obfuscator/
• http://www.wiseowl.com/products/products.aspx
• http://www.eziriz.com/comparison.htm

Taken from: http://forums.microsoft.com/MSDN/showpost.aspx?postid=420884&siteid=1

Step 1: Dis-assemble the assembly
ildasm myTest.dll /out:myTest.il

Step 2: Re-Assemble using your strong-name key
ilasm myTest.il /res:myTest.res /dll /key:myTest.snk /out:myTestSN.dll

This code work perfectly to assign strong name.

for verification you can use following command,
sn -vf myTestSN.dll

I’ve been aware of Microsoft’s documentation generation system called Sandcastle for a while now but only recently have I had a chance to use it.

With NDoc all but dead (see NDoc 2.0 Alpha) Sandcastle is now one of very few free alternatives that I could find to generate documentation from my coding comments. However, it did take a bit of searching and playing around to get things working.

[Read more]

Once you know it you'll probably never forget it...but wait, this is the second time I've googled for this. I'd best post how you "get the Windows temporary directory using C#"!