I am evaluating .NET Reactor for my Silverlight obfuscation. I have the demo version of 4.3.1.0, but I’m not getting the same results that you did. Perhaps this is because I’m not using a fully-licensed copy yet.
Following the steps that you list in your post, I get a new XAP file but only the primary assembly is obfuscated. None of the other assemblies (third-party or mine) are obfuscated.
I guess I would expect Reactor to obfuscate all the assemblies that you select on the Files tab and re-package the XAP with the obfuscated assemblies. In my case, it appears that only the main assembly gets obfuscated and re-packaged, and the other selected assemblies are obfuscated and placed in their own folder. Apparently, this means that I have to re-package the XAP manually; which is doable, but not preferred.
Did you have the same results with your use of .NET Reactor?
I had the same experience as Integragreg initially. However, I was able to figure it out. After selecting my .xap as the “Main Assembly,” I clicked Add under “Additional Files” and selected my .xap file again. At that point, all the other packaged assemblies were added, and I just removed the ones I didn’t want to be obfuscated.
I didn’t find anything in the help or a forum somewhere; it was a lucky guess. Hopefully this’ll help someone.
Comments on: "Demystifying Silverlight Obfuscation" (2)
I am evaluating .NET Reactor for my Silverlight obfuscation. I have the demo version of 4.3.1.0, but I’m not getting the same results that you did. Perhaps this is because I’m not using a fully-licensed copy yet.
Following the steps that you list in your post, I get a new XAP file but only the primary assembly is obfuscated. None of the other assemblies (third-party or mine) are obfuscated.
I guess I would expect Reactor to obfuscate all the assemblies that you select on the Files tab and re-package the XAP with the obfuscated assemblies. In my case, it appears that only the main assembly gets obfuscated and re-packaged, and the other selected assemblies are obfuscated and placed in their own folder. Apparently, this means that I have to re-package the XAP manually; which is doable, but not preferred.
Did you have the same results with your use of .NET Reactor?
I had the same experience as Integragreg initially. However, I was able to figure it out. After selecting my .xap as the “Main Assembly,” I clicked Add under “Additional Files” and selected my .xap file again. At that point, all the other packaged assemblies were added, and I just removed the ones I didn’t want to be obfuscated.
I didn’t find anything in the help or a forum somewhere; it was a lucky guess. Hopefully this’ll help someone.