This is a migrated thread and some comments may be shown as answers. Reducing XAP Size by using application library caching. Telerik Minifier. Hi all, I have one question i was trying to use the feature of silverlight whihc is reduce xap file size by using application library caching, i have two systems one one i had telerik installed and on another i didnt had telerik installed.
When i build the solution on the system having telerik installed everything worked like charm , but when i build up on the system which dont have telerik installed the xap size grew very large as it inlcluded all the telerik dlls inside it. So ideally this should not happen i then tried everything zipping down individual dlls and altering the appManifest.
So is how to use application library caching on a system where we dont have telerik installed. Same rule applies for any other third party assembly. One solution which is obvious and comes to mind is install the third party assembly files in the global assembly cache that too i tried but its of no help Can you sugggest me any solution to this problem.
Thanks, Aashish Gupta www. Add a comment. Submit comment. Sort by Score Date. Tina Stancheva Telerik team. Hello eraashishgupta, In order to take advantage of the application library chaching, you need to add the assemblies accompanied by a valid assemblyShortName.
Those files configure the assemblies for use with application library caching. You can read more here. If you open the binaries from your installation folder, you will notice that each dll file is accompanied by a mapping file and therefore you can reduce the size of your XAP. Add a comment. Active Oldest Votes. Improve this answer. Gone Coding Gone Coding You can check the "Reduce XAP size by using application library caching" option.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.
Email Required, but never shown. The Overflow Blog. In this post I'll try to summarize the five ways to reduce the size of a xap that I've shared today with Sofia's Silverlight User Group. In order to reduce the size of a xap file, we should first be aware of its structure. Basically it can contain only 4 things:. So we can smaller its size by reducing the code and resources of our assemblies, load assemblies on demand exclude them from the xap or minify some of the compiled library assemblies.
You should carefully think about the resources Images, Videos You have 3 options to choose from - embed them into assembly, add them as a content in the xap or leave them on the server as web content. Note that the last option can reduce the xap significantly. You have to check their "Build Action" and choose the correct one:.
Although the Prism give us so much flexibility and great features, it can't fix one problem that comes with using already compiled assemblies. The abstract problem is that it doesn't matter how much code or features you use from one assembly - you get it as a whole. This problem was addressed long time ago and the solution is named " Minification " the process of removing all unnecessary characters from source code, without changing its functionality.
This is very popular trick in the JavaScript world and it obviously makes sense - to reduce the size of a web page, by removing unused JS code. In the Telerik's Silverlight world the solution is called Assembly Minifier. It reduces the compiled assemblies size by removing the controls code and resources that your application doesn't need during run-time. The result is smaller assemblies, smaller xap, which results in faster download time and faster application loading.
Now, I have this amazing Silverlight 3 app that uses the charting components from the Silverlight Toolkit :. When I build the app, I see that the original. Xap file is KB. This is a debug build of the app, btw. Save the changes and then build your project. Now, we see that there are 3 new.
0コメント