Utility: Extmap Maker v1.1

Thursday, November 24, 2011

Quite some time ago, I wrote small utility which helped to create external map manifest file for Silverlight assemblies. This manifest is needed to enable XAP reduction feature (you can read more about it here). I have been told, that the utility is not working with assemblies compiled with Silverlight 5, so I decided to update it. The new version compatible with Silverlight 3, 4 & 5 assemblies. Please note, that new version requires .NET 4.0 Client profile in order to work. Updated version can be downloaded from here.   Stay tuned, Alex


Thursday, March 24, 2011

This year (3rd or 4th time in row) I’m attending MIX11 conference in Las Vegas. The conference takes place at Mandaly Bay Hotel April 12-14, 2011. The pre-conference boot camps are taking place April 11. If you want to meet and/or ask some Silverlight, XNA and Windows Phone 7 related questions I will be around from April 11. Also, 11 more colleagues from Sela (top rated senior .NET consultants) will be around – I could connect you with them! Drop me a message via Contact Form or tweet me @DevCorner.    ...

Thoughts about application packaging, Resources, MVVM and others

Sunday, October 24, 2010

I thought a lot before decided to write this post… First - I’d like to thanks Ariel Ben Horesh for “inspiring” me to write this post and for dedicating so much time to write his post! After reading his post I thought a lot and my thoughts about the post are the follows: 1. First, I thought about the applications and the way to provide user with best experience while loading those applications… The users shouldn’t wait minutes for application to download… While authoring large Silverlight applications (MVVM or not) the author should consider to split...

Utility: Extmap Maker

Thursday, July 16, 2009

Silverlight 3 has nice feature to reduce the XAP package size of application by providing external assembly parts. To enable this feature use Silverlight project properties: When this enabled, most of Microsoft assemblies will not reside inside XAP package, but as ZIP files alongside the XAP itself. The application manifest will point to those ZIP files. This will enable browser caching mechanism. Actually, compiler “decides” which assembly will could be used as external ZIP assembly by presence of valid external map manifest file alongside assembly. I’ll not describe what is in this manifest – those, who want to know...

Silverlight 3 Quick Tip #5: Assembly Caching

Sunday, March 29, 2009

Always wanted to have smaller XAP files and take control of external assemblies, that are not part of core runtime? Using Silverlight toolkit and want to cache this assemblies on client machines to keep the resulting XAP smaller? Well, if so new feature in Silverlight 3 Beta will help you. To enable assembly caching, in Silverlight project properties check “Reduce XAP size” checkbox: The effect are following: In standard non-checked compilation the XAP file has all the external assemblies being referenced from the application: The AppManifest.xaml looks like follows: <Deployment xmlns=http://schemas.microsoft.com/client/2007/deployment ...