How to choose right Silverlight Architecture/pattern and Template

Question

 

Hi teams.

I don't have much more experience on Sliverlight. Just I work 1 year on Sliverlight with multi xap architecture, I have confusion on How to choose right Sliverlight Architecture/pattern and Template.

Please go through the below lines…

We are migrate our asp.net web application to Sliverlight 4.0/5.0 i.e. we are developing the same application in Sliverlight    from scratch .This web application has around 50+ pages with business logic is in class library , Data Access layer is also class library  using ADO.Net and database as Sqlserver.

For this New Development process

1. We can use DAL layer as Ado.net Class library / ADO.Net Entity Farm work.
2. BAL needs to convert to WCF.
3. UI is Sliverlight.

When we focus on Sliverlight UI part we face a lot of confusion about "How to choose Sliverlight Architecture/pattern and Template" and which is the right one for us.

The suggested approaches are.

For a Single page single xap i.e. per page one project.

• Advantages

1. Overall xap size is reducing.
2. Page loaded quickly.
3. Good performance.

• Disadvantages

1. Difficult to maintain number of xap.
2. Difficult to give master page look and fill.
3. Difficult to pass parameter from page to page (only with query string, Isolated Storage not suggested.)

For a Single xap for project.

1. Advantages

i.                    Easy to Provide master page look and fill.

ii.                  Pass parameter from page to page (With query string, Isolated Storage, public property).

•  Disadvantages

§  Difficult to maintain State of application (i.e. state management) as this type of application has one entry point from APP.xaml  if user  Referees the page the state up page is loaded.

§  Overall xap size is Increase.

§  Performance point of view not so good.

Module wise xap for project (XAP on demand).

• Advantages

1.      Provide master page look and fill.

2.      Pass parameter from page to page (With query string, Isolated Storage, public property).

3.      Performance point of view it is better than single xap.

 

•  Disadvantages

§  Difficult to maintain State of application (i.e. state management) as this type of application has one entry point from APP.xaml  if user  Referees the page the state up page is loaded.

§  Overall xap size is Increase.

Sliverlight Template

As Microsoft provide three Templates for Sliverlight development, so which is the right one.

• Sliverlight Application
• Navigation Application
• Business Application.

Design Patterns:

• MVVM
• Prism
• Others.

If I have any mistakes please excuse me.

Your support/suggestions is highly appreciated and welcome...........

Thank's

Prasanta Kumar Pradan