Is Silverlight protection required?

I don’t quite understand how Silverlight code works in a browser. Are assemblies going to the client machine? Is there any chance of decompiling the code using Reflector or some similar tool? If so, what options do you need to protect the code? Scientists .net obfuscators working with Silverlight?

+5
source share
7 answers

To view the Silverlight application, the client downloads an .xap file containing the dll and one xml configuration and optional resources. The dll contains compiled C # code that runs in the Silverlight runtime on the client machine. Silverlight runtime is basically a subset of the full .net runtime. Thus, the user receives the code in the dll, and then can use the tools to get the source code. Therefore, the most you can do is obfuscation. Still for very critical code, which should not be an option. You can use some other method (WCF or other web services to hide part of your code, maybe), if it shows your needs.

+5
source

, -, . Javascript, Flash Silverlight.

, , API, .

+6

, silverlight, SilverlightSpy FirstFloor. .NET Reflector , ( ) , xaml .

( pragma no-cache, , URL-). , .

+2

, - , , . , .

+2

-No Cache- .xap , Silverlight. .xap temp internet.

https .xap

, -/.xap ( Joel)

+1

,

, SL .

+1

Yes, Silverlight xap files are nothing but zip files with your assemblies in them, so they need protection through obfuscation. Give Crypto Obfuscator - it obfuscates xap files directly, it can also obfuscate XAML files in your assemblies, renaming class references, deleting comments, spaces, newlines, etc.

0
source

All Articles