Comments on: More on optimizing XAP files http://designwithsilverlight.com/2009/02/19/more-on-optimizing-xap-files/ Silverlight... you're soaking in it. Sat, 13 Mar 2010 17:42:38 +0000 http://wordpress.org/?v=2.6 By: Silverlight http://designwithsilverlight.com/2009/02/19/more-on-optimizing-xap-files/#comment-1866 Silverlight Fri, 27 Feb 2009 12:27:25 +0000 http://designwithsilverlight.com/?p=147#comment-1866 Great Component!! Didn't knew the One XapOptimizer! Great article! I've wrote an article about Silverlight too: <a href="http://www.q-5.nl/blog/webdesign/silverlight-de-informatie-die-je-nodig-hebt/" title="Silverlight" rel="nofollow">Silverlight</a> Regards, Mark Great Component!! Didn’t knew the One XapOptimizer! Great article! I’ve wrote an article about Silverlight too:

Silverlight

Regards,
Mark

]]> By: bernardo http://designwithsilverlight.com/2009/02/19/more-on-optimizing-xap-files/#comment-1864 bernardo Fri, 20 Feb 2009 15:53:10 +0000 http://designwithsilverlight.com/?p=147#comment-1864 Hi Jeff. Just to clarify: The XapOptimizer reduces Xap size in three ways. 1) Removal of unused classes/resources. Of course, you would never deliberately add stuff that you don't use to a project. But many projects use libraries that contain a large number of classes, and they only need/use a few. One good example is C1.Silverlight.dll, the original motivation for creating the XapOptimizer. This is by far the most important feature of the XapOptimizer. 2) Obfuscation. In addition to protecting your IP, obfuscation reduces code size by shortening identifier names. 3) Better zip compression. You said the reduction in your tests is about equivalent to unzipping and re-zipping. This is probably because your tests did not use any third party libraries. I hope you find this information useful. And thanks for trying the XapOptimizer. Hi Jeff.

Just to clarify: The XapOptimizer reduces Xap size in three ways.

1) Removal of unused classes/resources. Of course, you would never deliberately add stuff that you don’t use to a project. But many projects use libraries that contain a large number of classes, and they only need/use a few. One good example is C1.Silverlight.dll, the original motivation for creating the XapOptimizer. This is by far the most important feature of the XapOptimizer.

2) Obfuscation. In addition to protecting your IP, obfuscation reduces code size by shortening identifier names.

3) Better zip compression.

You said the reduction in your tests is about equivalent to unzipping and re-zipping. This is probably because your tests did not use any third party libraries.

I hope you find this information useful. And thanks for trying the XapOptimizer.

]]>