This is a feature suggestion list dedicated to the core WCF RIA Services suggestions. Find out more information about RIA Services at http://silverlight.net/riaservices.
If you have questions, need help or find a bug in RIA Services, visit the forums at
http://forums.silverlight.net/forums/53.aspx
-
642 votes
Support data change notifications from the server
Ability for the client to asynchronously receive notificaitons from the server whenever the data in the client's context has changed on the server (possibly as a result of another user's action).
-
577 votes
-
527 votes
-
521 votes
-
360 votes
Support for WPF
Do code generation for WPF the same way Silverlight does (except taking advantage of any WPF-specific features, of course).
-
214 votes
-
174 votes
Support more of OData
Support all the types of filtering, updating, etc. that OData supports.
-
172 votes
EntityQuery<T>.Select() to project entities from the RIA Clients without creating DTOs at the server
This is very important..creating DTO's at the service just to fullfil some specific view requirements is very painful and incorrect!
We just be able to project entities just like WCF Data Services does.
-
135 votes
A visual plugin for VS to manage domain services
It would be great to extend the current wizard to be able to manage the service visually as the tables change during development.
-
121 votes
-
121 votes
Ability to Include Navigation Properties Based on Many-to-Many relationships
Currently, when you apply the Include and Association attributes in the Domain Service MetaData class, you cannot add an association based on a many to many relationship since the keys don't match.
-
118 votes
-
102 votes
-
92 votes
Authorization-based UI (admin/user have different UI)
Propagate authorization/role metadata from server to client so that it can be used for building authorization-specific UI; e.g. admin sees additional named update methods that a user does not.
-
83 votes
Paging support without requiring LINQ backend (e.g. sprocs)
Enable paging over sprocs / non-IQueryable sources. Map client-side paging infrastructure to DomainService query method parameters.
-
67 votes
Transaction support from client
So that multiple calls to SubmitChanges() of different domain contexts can we wrapped into a TransactionScope()
-
66 votes
RIA Service support for ORM's besides EF
Would love to point the RIA Svs Wizard at some mapping file in NHibernate or LLBLgen and have it work, understand entities in the ORM etc.
-
48 votes
RIA Client for DataSet returning web services
Use web services returning/consuming DataSet on the server and get DomainContext to provide RIA experience with those web-services.
-
36 votes