how to evade Silverlight cross-domain security law?
The other posters have answered your question–or rather, the question you should have asked–so I’m probably wasting my breath. But it might help–not only help us to read your question, but help you to resolve it on your own–if you try to reframe it in a more useful way. Instead of asking, “How do I do X,” where X is something that cannot be done by design, you should ask, “What alternatives are there to doing X, since X cannot be done by design?” In this case, the Silverlight cross-domain restriction is a security feature that’s intended to be impossible to evade (and as rjmunro points out, even if there were a way around it, you wouldn’t want to build a product upon it, since it will almost certainly be closed in the future). There’s another reason to ask yourself about alternatives that can fill the same role: this question focuses your attention on the security purpose of the cross domain restriction. If you ask yourself how to “evade” the cross domain restriction, you may well
