How does the performance of a Silverlight web browser application depend on the number of pages or child pages in the application?

Question

If you have practical experience deploying Silverlight applications for image viewing and deep scaling, does the number of application pages affect performance? Say load or run time, display time, etc.

It is necessary to provide users with a multitude of dedicated interfaces for viewing and processing images, including deepzoom images.

What's better:

• have one application containing 5 pages to display various image user interface options with 3 child windows per page (total 15 pages) or
• have 5 different applications with one main page and three child pages. but make them work together through webservices or just linking html pages at runtime.

Any thoughts? Thanks Val

Answer 1

There are 2 questions here.

• Initial boot time and
• Actual performance

Download time / application size:

( ) . , Siverlight, ( ). , . - 10 , , Silverlight.

. , Silverlight XAP ( ).

, , , - , . MEF Prism .

, , .

• (, , )
• ( , Silverlight).
• (, - , ).

, , .

:

• -/ , MEF , .
• , .
• 1- , .

, .