blocks|key|297882|text|RIA服务是一种服务器端技术，它自动生成客户端(Silverlight)对象，这些对象负责与服务器的通信，并提供客户端验证。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|297883|RIA服务中的主要对象是DomainService，通常是连接到LinqToEntities模型的LinqToEntitiesDomainService。|offset|length|style|CODE|297884|在RIA服务中要记住的关键一点是，它主要是一个复杂的构建技巧。创建域服务并编译解决方案时，将生成域服务的客户端表示形式。此客户端表示具有相同的接口。假设您使用IQueryable<Customer>+GetCustomersByCountry方法创建了一个服务器端域服务CustomerService。当您构建解决方案时，会在您的Silverlight项目中生成一个具有GetCustomersByCountryQuery方法的名为CustomerContext的类。现在，您可以在客户端使用此方法，就像在服务器上调用它一样。|297885|更新、插入和删除遵循不同的模式。创建域服务时，可以指示是否要启用编辑。然后，在服务器端域服务中生成相应的更新/插入/删除方法。但是，客户端部分没有这些方法。您的CustomerContext上有一个名为SubmitChanges的方法。那么这是如何工作的呢：|297886|对于更新，您只需更新现有客户的属性(通过GetCustomersByCountryQuery).|297887|For+inserts检索，使用CustomerContext.Customers.Add(new+Customer(...)+{...}).|unordered-list-item|297888|
|297889|For+|297890|297891|，使用CustomerContext.Customers.Remove(someCustomer).|297892|297893|编辑完成后，调用CustomerContext.SubmitChanges()。|297894|至于验证，您可以使用System.ComponentModel.DataAnnotations名称空间中的验证属性来修饰服务器端对象。同样，在构建项目时，现在会自动为相应的客户端对象生成验证代码。|297895|我希望这个解释能帮助你更进一步。|297896|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/system.servicemodel.domainservices.server.domainservice(VS.91).aspx)|1|http://msdn.microsoft.com/en-us/library/ff423019(VS.91).aspx|2|http://msdn.microsoft.com/en-us/library/system.componentmodel.dataannotations.aspx^0|0|C|D|1D|R|C|D|0|1D|R|1|0|27|16|3R|F|55|Q|60|F|0|28|F|2T|D|0|K|Q|0|G|1I|0|0|0|0|3|1A|0|0|8|V|0|A|11|A|11|2|0|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@$D|1I|E|1J|F|G]|$D|1K|E|1L|F|G]]|9|@$D|1M|E|1N|1|1O]|$D|1P|E|1Q|1|1R]]|A|$]]|$1|H|3|I|5|6|7|1S|8|@$D|1T|E|1U|F|G]|$D|1V|E|1W|F|G]|$D|1X|E|1Y|F|G]|$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|21|8|@$D|22|E|23|F|G]|$D|24|E|25|F|G]]|9|@]|A|$]]|$1|L|3|M|5|6|7|26|8|@$D|27|E|28|F|G]]|9|@]|A|$]]|$1|N|3|O|5|P|7|29|8|@$D|2A|E|2B|F|G]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|2C|8|@]|9|@]|A|$]]|$1|S|3|T|5|P|7|2D|8|@]|9|@]|A|$]]|$1|U|3|R|5|6|7|2E|8|@]|9|@]|A|$]]|$1|V|3|W|5|P|7|2F|8|@$D|2G|E|2H|F|G]]|9|@]|A|$]]|$1|X|3|-4|5|6|7|2I|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|2J|8|@$D|2K|E|2L|F|G]]|9|@]|A|$]]|$1|10|3|11|5|6|7|2M|8|@$D|2N|E|2O|F|G]]|9|@$D|2P|E|2Q|1|2R]]|A|$]]|$1|12|3|13|5|6|7|2S|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|2T|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]|1C|$5|17|18|19|A|$1A|1D]]|1E|$5|17|18|19|A|$1A|1F]]]]

RIA services is a server-side technology that automatically generates client-side (Silverlight) objects that take care of the communication with the server for you and provide client-side validation.

The main object inside a RIA service is a <a href="http://msdn.microsoft.com/en-us/library/system.servicemodel.domainservices.server.domainservice(VS.91).aspx" rel="noreferrer"><code>DomainService</code></a>, usually a <a href="http://msdn.microsoft.com/en-us/library/ff423019(VS.91).aspx" rel="noreferrer"><code>LinqToEntitiesDomainService</code></a> that is connected to a LinqToEntities model.

The key thing to remember in RIA services is that it's mainly a sophisticated build trick. When you create a domain service and compile your solution, a client-side representation of your domain service is generated. This client-side representation has the same interface. Suppose you create a server-side domain service <code>CustomerService</code> with a method <code>IQueryable&lt;Customer&gt; GetCustomersByCountry</code>. When you build your solution, a class is generated inside your Silverlight project called <code>CustomerContext</code> that has a method <code>GetCustomersByCountryQuery</code>. You can now use this method on the client as if you were calling it on the server.

Updates, inserts and deletes follow a different pattern. When you create a domain service, you can indicate whether you want to enable editing. The corresponding methods for update/insert/delete are then generated in the server-side domain service. However, the client-side part doesn't have these methods. What you have on your <code>CustomerContext</code> is a method called <code>SubmitChanges</code>. So how does this work:

<ul>
<li>For updates, you simply update properties of existing customers (that you retrieved via <code>GetCustomersByCountryQuery</code>).</li>
<li>For inserts, you use <code>CustomerContext.Customers.Add(new Customer(...) {...})</code>.</li>
<li>For deletes, you use <code>CustomerContext.Customers.Remove(someCustomer)</code>.</li>
</ul>

When you're done editing, you call <code>CustomerContext.SubmitChanges()</code>.

As for validation, you can decorate your server-side objects with validation attributes from the <a href="http://msdn.microsoft.com/en-us/library/system.componentmodel.dataannotations.aspx" rel="noreferrer"><code>System.ComponentModel.DataAnnotations</code></a> namespace. Again, when you build your project, validation code is now automatically generated for the corresponding client-side objects.

I hope this explanation helps you a little further.

blocks|key|297916|text|最新消息:+WCF+RIA服务已死：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|297917|http://blogs.msmvps.com/deborahk/who-moved-my-cheese-ria-services/|offset|length|297918|如果你想使用RIA服务，它们已经是开源的：|297919|http://www.openriaservices.net/blog/posts/|297920|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|1U|0|0|0|0|16|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$D|Y|E|Z|1|10]]|A|$]]|$1|J|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|C]]|Q|$5|M|N|O|A|$P|I]]]]

The latest news: WCF RIA Services is dead:

<a href="http://blogs.msmvps.com/deborahk/who-moved-my-cheese-ria-services/">http://blogs.msmvps.com/deborahk/who-moved-my-cheese-ria-services/</a>

If you want to use RIA Services, they have been open sourced:

<a href="http://www.openriaservices.net/blog/posts/">http://www.openriaservices.net/blog/posts/</a>

I hate MSDN's site for WCF RIA services. It does not say what it is, it only says what it does. It says what it can achieve but does not say why I need it. 

For example:

<blockquote>
 "A common problem when developing an
 n-tier RIA solution is coordinating
 application logic between the middle
 tier and the presentation tier".
</blockquote>

Well, it does not mean much to me.

<blockquote>
 "RIA Services solves this problem by
 providing framework components, tools,
 and services that make the application
 logic on the server available to the
 RIA client without requiring you to
 manually duplicate that programming
 logic. You can create a RIA client
 that is aware of business rules and
 know that the client is automatically
 updated with latest middle tier logic
 every time that the solution is
 re-compiled."
</blockquote>

So does it download DLLs from server? Is it a metadata describing the rules for the data?

So what is it? Is it just a VS 2010 add-on for RAD? Or is it a technology on top of WCF or underneath it or what? Where does it live? With data, with server, what?

I appreciate if you can summarise this for me please.

What is WCF RIA services?

服务器

我讨厌MSDN的WCF RIA服务站点。它没有说它是什么，它只说它做了什么。它说明了它能实现什么，但没有说明我为什么需要它。例如：“在开发n层RIA解决方案时，一个常见的问题是协调中间层和表示层之间的应用逻辑”。好吧，这对我来说没什么意义。 "RIA服务通过提供框架组件、工具和服务来解决这个问题，这些组件、工具和服务使...

问什么是WCF RIA服务？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是WCF RIA服务？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是WCF RIA服务？
EN