Redundancy of application size.

Dec 14, 2008 at 1:40 PM
Hi,

For example we have 6 modules which uses Toolkit controls. So, we will get 6 xap packages with Toolkit dll files (about 200Kb). As a result redundancy of application size will be about (6-1)*200kb.

Thanks,
Zakharov Alexey.
Dec 14, 2008 at 2:26 PM
I find dirty solution to the problem. We can add refence to assemblies which need to be shared to assembly with shell.xaml. And after build we can manually delete from module xap files assemblies which are shared.
Dec 14, 2008 at 3:14 PM
interesting!

btw, are you using the multi-targeting feature of Prism v2? I'm facing a lot of problems with that since Silverlight is so weak if we compare it with WPF.
Dec 14, 2008 at 4:50 PM
Lexer, 
to avoid including toolkit in every xap file, you can disable property "Copy to output directory" (I don't remember exactly) in properties of added reference.
Also, you can reduce size of the xap file, by repacking it with more aggresive zip-program.
Dec 14, 2008 at 7:10 PM
>> btw, are you using the multi-targeting feature of Prism v2? I'm facing a lot of problems with that since Silverlight is so weak if we compare it with WPF.

Now, we are trying to adopt modularity ondemand loading to make our silverlight application load faster.

>> to avoid including toolkit in every xap file, you can disable property "Copy to output directory" (I don't remember exactly) in properties of added reference.

There is a property "copy local" and we can set it to false. Thanks.

>> Also, you can reduce size of the xap file, by repacking it with more aggresive zip-program.

I'm not a great specialist in zipping =) But are you sure that this trick won't make my application unreadable? =)