Sun, March 9, 2008, 10:40 AM under Silverlight
When you build a Silverlight 2 application, you compile your source files (inc. XAML and embedded resources) into assemblies (dlls). Those assemblies (plus any 3rd party ones plus MS assemblies that are not part of Silverlight) are then collected together along with a manifest into a packaged archive – or in other words, a ZIP file. Except, the extension is changed to be a .XAP (pronounced "ZAP"). The benefits of packaging everything into a XAP should be obvious but in case they are not, Pete has discussed that on his blog (inc. screenshots)
. Note that if your web server is on IIS (prior to version 7) you need to register that MIME type
. As an aside, my web server happens to be Apache (shocking I know!) and I had to configure nothing – it just worked.
So, if I had given you a Winforms EXE file you wouldn't ask me for the source code, you would probably just pass it through your favourite decompiler and you've got it all. Same with Silverlight apps: if I point you to my web page that is running a Silverlight app (e.g. the one from this post
) all you have to do is:1. View HTML source
, e.g. for this: http://www.danielmoth.com/SL/HtmlBridge/index.html2. Locate the tag that points to a XAP file
and copy the full path, e.g. ClientBin/DemoIntegration.xap3. Use that path to "Save As"
the xap file locally.4. Rename the XAP file to ZIP
and explode it to get the DLLs inside.5. Party away by tossing the DLL(s) to the decompiler
, e.g. Reflector.
Obviously authors of serious SL apps may not condone that behaviour, but feel free to do it with all of mine, for example the DeepZoom/MultiScaleImage that I have now updated to also use mouse wheel