Next week, I'll be doing a presentation on ADO.NET Data Services for Visug. While creating some demo's, I found myself in a bit of problems when debugging.
By default, Data Services don't return information on what's wrong when you try to execute some code, for example an update, against it. This is understandable: if you open up a data service on the web, you shouldn't be returning all important information about entities in the underlying model.
However, when developing a Data Service, it might be handy to get a little more information than just "An error occurred while processing this request". Here's how to achieve this...
You can start by setting the UseVerboseErrors on the ServiceConfiguration to true, like so:
public
{
config.UseVerboseErrors =
}
This will get you the error returned by the model/database. For example, you'll see that you are inserting duplicate keys in your tables.
Now, this is OK if you are able to run your service. But what if it doesn't even start? You'll get the generic error: "The server encountered an error processing the request". Trying to get more info with the above method won't help you, since the service didn't even execute anything.
In that case, you can use the following attribute on your service class:
[System.ServiceModel.
These 2 options should provide you with enough information about what's going wrong with your services. Do remember to remove them when you go live with the application!
Ads by The Lounge
All content is property of www.snowball.be. Nothing on this site can be copied or published elsewhere, unless otherwise stated.
This site is made by Gill Cleeren.
Questions? Opinions? E-mail