问题描述
我们正处在创建n层Silverlight的LOB应用程序，并正在考虑使用.NET RIA服务的中间。我们都不清楚在哪里这符合有关我们目前的WCF服务的API。我们目前的架构是：
We are in the middle of creating an n-tier Silverlight LOB application and are considering the use of .NET RIA Service. We are unclear where this fits in relation to our current WCF service API. Our Current architecture is:
的Silverlight ＆LT; - > WCF服务＆LT; - > 商业逻辑＆LT; - > 实体框架模型＆LT; - > 数据库
Silverlight <--> WCF Service <--> Business Logic <--> Entity Framework Model <--> Database
看着自己Nikhils混合09 presentation这样看来，.NET RIA服务将取代我们WCF和BusLog部分：
Having watched Nikhils Mix 09 presentation it would appear that .NET RIA Services would replace our WCF and BusLog sections:
的Silverlight ＆LT; - > RIA服务＆LT; - > EF型号＆LT; - > 数据库
Silverlight <--> RIA Services <--> EF Model <--> DB
这很好，希望我们需要有一个标准的SOAP端点API提供供其它应用程序（的Biztalk，集成等）使用。可.NET RIA服务公开为SOAP端点不异步要求？
Which is fine, expect that we need to have a standard SOAP endpoint API exposed for use by other applications (Biztalk,Integration etc). Can .NET RIA Services be exposed as SOAP endpoints without the asynchronous requirement?
有多容易实现了一个.NET RIA服务WCF服务？你知不知道这有什么好的网上的例子？
How easy is it to implement a WCF service over a .NET RIA Service? Do you know any good online examples of this?
谢谢，马克
推荐答案
是 - 在未来CTP的RIA服务我们将不得不用于定义WCF服务（通过道夫和最终香草WCF）一些很好的支持，公开你的业务逻辑在RIA服务。所以，你必须对你的RIA服务实现两个头。
Yes – In the next CTP for RIA Services we will have some very nice support for defining WCF service (via Astoria and eventual vanilla WCF) that exposes your business logic in RIA Services. So you’d have two heads on your RIA Services implementation.
Silverlight的＆LT; ---> RIA服务＆LT; ---> EF型号和LT; ---> DBWCF服务＆LT; --->
Silverlight <---> RIA Services <---> EF Model <---> DBWCF Services <--->
我会说这个模型是有道理的，如果主要目标是Silverlight应用程序，但是，如果主要目标是WCF服务，我想今天跟大家有模型挂..帮助吗？
I’d say this model makes sense if the primary goal is the Silverlight application, however if the primary goal is the WCF service, I’d hang with the model you have today.. Does that help?
..布拉德
这篇关于.NET RIA服务/ WCF服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！