ADO.NET Data Services - Tracing Messages from Client to Service
By : Mike Taultys Blog | On : 2008 January 02
I (very foolishly) spent a few minutes today trying to figure out why applying WCF tracing configuration to a ADO.NET Data Services client (i.e. a proxy generated with webdatagen.exe) wasn't producing me any tracing results. It didn't take too long to realise that the client proxy isn't actually a WCF proxy. It just uses HttpWebRequest directly. If you want WCF tracing, put your configuration onto your service side code. I didn't actually find WCF that useful in tracing messages here and so fell back to ...
|
|
|
Total:
 |
Click here to continue on details
Content Ownership
The content of this posting is wholly owned by Mike Taultys Blog, and as such: the same retains sole copyright for the content. softlogger.com is not responsible for this content.
Recommended Related Readings :
ADO.NET Data Services - Exposing Arbitrary Data (1)
I've been playing over Xmas with exposing arbitrary data from an ADO.NET Data Service and I wa...
ADO.NET Data Services - Inserting Related Entities
I spent some time with ADO.NET Data Services sitting atop of Entity Framework today trying to ...
Finding Data in Client Certificates
Can I pass additional user data, such as identity information, in a message secured with a c...
ADO.NET Data Services - Exposing Arbitrary Data (2)
Following on from the previous post, I wanted to look at how we can make our arbitrary data so...
ADO.NET Data Services - LINQ to SQL and Associations
One of the things that I didn't mention (because I didn't know and I'm still not 100% sure :-)...
Which Client Credential Does TransportWithMessageCredential Use?
I’m trying to use a Certificate credential with security mode TransportWithMessageCredential. ...
