Open RIA Services User Support WCF RIA Services question will be allowed here as well.  Viewed 1955142 time(s), 6 post(s)., 7/17/2013 8:55:56 PM - by ColinBlair

ColinBlair 7/17/2013 8:55:56 PM

In general, I will be answering questions on the WCF RIA Services board on MSDN as well, but MSDN has recently made their boards less user friendly so I am fine with answering WCF RIA Services questions here.

This content has not been rated yet. 
1539 Reputation 130 Total posts
jr 12/5/2013 4:15:47 PM

Colin -- First, thanks for your work on WCF RIA.

I guess I'll be the first to post here and see if it reaches you.

I have a situation where the service metadata buddy is not being generated in what looks to be a specific scenario. Unfortunately I'm not sure what exactly the scenario is.

I have a many-to-many table. Let's call it EmployeeDepartment . I want to fetch all departments for a given employee and fetch the department name with an [include]. I cannot get any metadata to generate on this table, and if I only include the EmployeeDepartment and Department tables in the wizard for creating a new service class, no metadata file is generated.

Give that I have a many-to-many here, is that the answer to my question? That is, it's not supported?

This content has not been rated yet. 
7 Reputation 1 Total posts
ColinBlair 12/5/2013 6:06:54 PM

You need to have the linking table in your model. So, you need Employee, Department, and EmployeeDepartment. The metadata file will not generate if it already exists, so check to make sure you don't have an old one laying around.

As an alternative, take a look at the Fluent configuration system in RIA Services Contrib. We will be moving to that eventually as the  preferred method of configuration.

This content has not been rated yet. 
1539 Reputation 130 Total posts
FuzzSchroeder 5/6/2015 3:10:13 PM

I have a legacy RIA Services project that is going through a security audit. They are modifying the requests in a tool like fiddler so that a guid does not deserialize. The code then blows up in the DomainServiceWebHttpBehavior.WebHttpQueryDispatchMessageFormatter.System.ServiceModel.Dispatcher.IDispatchMessageFormatter.DeserializeRequest(Message message, Object[] parameters)

 call and includes the full stack of the error in the Fault. The inclusion of the stack trace is considered a security issue even though it does not even get to our code.

I have been looking for a way to configure the service so that the stack trace is not included but have not found the right setting.
<serviceDebug includeExceptionDetailInFaults="false"/> -- does not seem to do it.
DomainServicesSection only has endpoints.

I am looking for a quick way to get this done without creating a new IDispatchMessageFormatter, or at least find a documented solution. Any thoughts would be much appreciated.


This content has not been rated yet. 
5 Reputation 1 Total posts
ColinBlair 5/18/2015 6:00:57 PM

The should be controlled by the Custom Errors setting in the System.Web section your web.config. If customErrors doesn't exist or or set to something other than Off then the stack trace shouldn't be leaking back to the client.

This content has not been rated yet. 
1539 Reputation 130 Total posts
rfrick 6/19/2015 5:32:08 AM

Colin, what do you think? Are we going to be able to compile to the web using Silverlight? :)

This content has not been rated yet. 
134 Reputation 10 Total posts