CODEWITHSUNDEEP
.netsilverlightsilverlight-4.0
Brian Mains
Brian Mains

Reputation: 50728

Larger Silverlight Project Implementations

As Silverlight applications become larger and larger, is it wise to break out an application into separate smaller applications by functional area, to keep the total xap file size lower? Is download size a concern for any silverlight developers, or is it OK because of the way that it can be downloaded and cached on the client?

Thanks.

Upvotes: 1

Views: 67

Answers (2)

O.O
O.O

Reputation: 11317

Take a look at Prism. Keeping an eye on the size of the xap file is crucial. As an end-user I'm not generally going to wait for something to load, I'll just move on to another site. Prism will help because it allows you to "easily" load modules on demand. This includes being able to load "modules" at app startup or in the background or a mix.

Upvotes: 1

Phil Murray
Phil Murray

Reputation: 6554

I would say keeping each XAP small aids in the overall performance of the application. I have also implementation MEF in some areas of a large business application for dynamic loading of XAP files

MEF

You are good to go with MEF in .Net 4 as its in the framework

Upvotes: 0

Related Questions