The process for using SmartAssembly with Silverlight applications is similar to the process for other types of application but you should be aware of the following point:

Silverlight .xap files are actually ZIP archives containing a manifest file (.xaml) and the required code, which is compiled as .dll files.

When you choose a .xap file in the project settings window, SmartAssembly reads the XAML file, and locates the DLL that is designated as the EntryPointAssembly.

SmartAssembly treats that DLL as the main assembly. You can prune code from it, merge and embed dependencies and add error reporting code to it, in the usual way.

When you build the assembly, however, SmartAssembly will build the complete .xap file.

Some of SmartAssembly's features will not work with Silverlight applications due to technical limitations in Silverlight. The features which will not work are:

• tamper protection
• references dynamic proxy
• compression and encryption of resources
• strings encoding with improved protection
• prevent disassembly of the resulting IL
• reducing the amount of allocated memory
• feature usage reporting
• unverifiable control flow obfuscation

Because Silverlight applications are compiled into DLLs, public members are automatically excluded from obfuscation.