本文介绍了wpf对数据库的缺点的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!
问题描述
MVVM - 模型视图模型, en.wikipedia/wiki/Model_View_ViewModel [ ^ ], MVC - 模型 - 视图 - 控制器, en.wikipedia/wiki/Model-view-controller [ ^ ]), MVA - 模型 - 视图-Adapter, en.wikipedia/wiki/Model-view -adapter [ ^ ], MVP - 模型 - 视图 - 演示者, en.wikipedia/wiki/Model-view-presenter [ ^ ]。 -SA MVVM — Model View View Model,
en.wikipedia/wiki/Model_View_ViewModel[^],
MVC — Model-View-Controller,
en.wikipedia/wiki/Model-view-controller[^]),
MVA — Model-View-Adapter,
en.wikipedia/wiki/Model–view–adapter[^],
MVP — Model-View-Presenter,
en.wikipedia/wiki/Model-view-presenter[^].
—SA Nothing. WPF is a presentation technology that has absolutely nothing to do with database access.There are no disadvantages of WPF as such - it depends on what you are trying to do.
Building a web app with WPF may be slightly tricky.
Crystal Reports - I don''t think crystal reports are installed in any express editions.
wpf在sql server 2005和visual studio 2012 Express中的水晶报告有什么缺点?
解决方案没有缺点,原因很简单: WPF与数据库无关。在.NET中,人们几乎总是使用ADO.NET。可以使用带或不带WFP的ADO.NET,带或不带ADO.NET的WPF。 不仅问题没有意义,而且你的想法作为开发人员对您来说很危险。这意味着你很难理解一个基本原则:关注点分离。 请参阅: en.wikipedia/wiki/Separation_of_concerns [ ^ ]; en.wikipedia/wiki/ADO.NET [ ^ ], msdn.microsoft/en-us/library/aa286484.aspx [ ^ ]; en.wikipedia/wiki/Windows_Presentation_Foundation [ ^ ]; msdn.microsoft/en-us/library/ms754130.aspx [ ^ ]。 此外,用户界面非常好代码的特殊方面。是应该尽可能分开。为了了解现有方法,我建议学习以下架构模式( http: //en.wikipedia/wiki/Architectural_pattern_(computer_science) [ ^ ]):
没什么。 WPF是一种与数据库访问完全无关的表示技术。
WPF没有这样的缺点 - 这取决于你想要做什么。 使用WPF构建Web应用程序可能有点棘手。 Crystal Reports - 我不认为任何快速版本都安装了水晶报告。
what are the disadvantage of wpf on sql server 2005 and crystal reports in visual studio 2012 express?
解决方案 No disadvantages, by one simple reason: WPF has nothing to do with databases. In .NET, people almost always work with ADO.NET. One can use ADO.NET with or without WFP, and WPF with or without ADO.NET. Not only the question makes no sense, but your thinking is dangerous for you as a developer. It means that you hardly understand one basic principle: separation of concerns. Please see: en.wikipedia/wiki/Separation_of_concerns[^]; en.wikipedia/wiki/ADO.NET[^], msdn.microsoft/en-us/library/aa286484.aspx[^]; en.wikipedia/wiki/Windows_Presentation_Foundation[^]; msdn.microsoft/en-us/library/ms754130.aspx[^]. Also, the UI is a very special aspect of code. Is should be separated as well as possible. To get an idea of existing approaches, I would advise to learn the following architectural patterns (en.wikipedia/wiki/Architectural_pattern_(computer_science)[^]):更多推荐
wpf对数据库的缺点
发布评论