4 comments

Add a comment…

Sign in

prestine

Your email address

Check!

invalid email

(thinking…)

Reset

or sign in with

• 
• 

UserVoice password

Forgot password?

Create a password

Your name

I agree to the terms of service

Signed in as (Sign out)

Close

Close

Post comment Submitting...

• Miguel Madero commented  ·  August 4, 2010 3:45 a.m.  ·  Delete

  Obfuscators should do the trick.
  Is important to consider that although this might look like a Silverlight issue/limitation, any client technologiy is equally or more vulnerable (e.g. WPF, AJAX, Winforms, etc)

• Marc Roussel commented  ·  April 16, 2010 9:34 a.m.  ·  Delete

  No thank you obfuscating obfustates nothing.

• Marc Roussel commented  ·  April 16, 2010 9:28 a.m.  ·  Delete

  Since I can't edit my comment, There's a typo. it's decompile not recompile
  And it's xap not xamp

• Stefan Olson commented  ·  November 18, 2009 3:15 p.m.  ·  Delete

  You can use an obfuscator to make it more difficult. You can read my review at this site: http://www.olsonsoft.com/blogs/stefanolson/post/Selecting-an-obfuscator-for-Silverlight.aspx