问题描述
团队.
我在Sliverlight上没有更多的经验.我在具有多xap架构的Sliverlight上工作了1年，我对如何选择正确的Sliverlight架构/图案和模板感到困惑.
请通过以下几行...
我们将asp.net Web应用程序迁移到Sliverlight 4.0/5.0，即我们正在从头开始在Sliverlight中开发相同的应用程序.此Web应用程序具有约50多个页面，业务逻辑在类库中，数据访问层也是使用以下类的类库ADO.Net和数据库作为Sqlserver.
针对此新开发流程
1.我们可以使用DAL层作为Ado.net类库/ADO.Net Entity Farm的工作.
2. BAL需要转换为WCF.
3. UI是Sliverlight.
当我们专注于Sliverlight UI部分时，会遇到很多关于如何选择Sliverlight体系结构/模式和模板"的困惑，而这正是我们的正确选择.
建议的方法是
对于单页xap，即每页一个项目.
o优势
1.总体Xap尺寸正在减小.
2.页面快速加载.
3.良好的表现.
o缺点
1.难以保持Xap的数量.
2.难以赋予母版页外观和填充感.
3.难以在页面之间传递参数(仅使用查询字符串，不建议使用隔离存储.)
用于项目的单个xap.
1.优势
一世.易于提供母版页外观和填充.
ii.在页面之间传递参数(带有查询字符串，隔离存储，公共属性).
o缺点
难以维护应用程序状态(即状态管理)，因为如果用户引用了加载状态向上页面的页面，则该类型的应用程序从APP.xaml具有一个入口点.
总体Xap大小为增加".
性能方面不太好.
针对项目的模块化明智xap(按需XAP).
o优势
1.提供母版页外观和填充.
2.在页面之间传递参数(带有查询字符串，隔离存储，公共属性).
3.从性能的角度来看，它比单个xap更好.
o缺点
难以维护应用程序状态(即状态管理)，因为如果用户引用了加载状态向上页面的页面，则该类型的应用程序从APP.xaml具有一个入口点.
总体Xap大小为增加".
Sliverlight模板
由于Microsoft提供了三个Sliverlight开发模板，因此正确的模板就是一个.
o Sliverlight应用程序
o导航应用程序
o业务应用程序.
设计模式:
o MVVM
o棱镜
o其他.
如果我有任何错误，请原谅.
非常感谢您的支持/建议......
谢谢's
Prasanta Kumar Pradan
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.
oAdvantages
1.Overall xap size is reducing.
2.Page loaded quickly.
3.Good performance.
oDisadvantages
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).
o 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).
oAdvantages
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.
o 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.
oSliverlight Application
oNavigation Application
oBusiness Application.
Design Patterns:
oMVVM
oPrism
oOthers.
If I have any mistakes please excuse me.
Your support/suggestions is highly appreciated and welcome...........
Thank''s
Prasanta Kumar Pradan
推荐答案
这篇关于如何选择正确的Sliverlight体系结构/模式和模板.的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！