wcf-data-services

Problem: DataServiceContext.SaveChanges() fails with "302 - moved" response. Background/Suspected Cause: Load balancer! - We recently changed our infrastructure so that our web servers now sit behind a load balancer which also handles the ssl. Clients address the service as HTTPS but IIS ends up processing HTTP requests since the SSL was done by the load balancer(I am sure most of you are familiar with this type of setup). Anyway, what we end up with is a feed that contains URIs that are using HTTP rather than HTTPS. (see GET request/response below with http in the response instead of httpS).

I have an ADO.NET data service exposed by a .NET app (not IIS) which is consumed by a .NET client app. Some calls to this data service return large amounts of data. I'd like to compress the XML data on the wire to reduce payload and improve performance. Is this possible? I assume you're hosting using WCF in your .NET "app"? If so, you would need write some custom MessageEncoder implementation because WCF does not provide this out of the box. Luckily there is a sample in the SDK that you can use. I actually just realized that this is only step one of two depending on whether or not your client

I've had a WCF Data service published for about 2 months. It's 100% been hacked already. I even noticed the service published on twitter! Luckily my site was under development and the user entity was only about 80 beta testers. Still this is a pretty big problem. With the power of E.F. Navigation properties anyone can easily write a script to download all my user data and my valuable domain data that no-one else has. I want to provide non-authenticated access and do things like: Limit what columns get exposed (e.g. a users emails) Limit number of requests possible per day (e.g. 10 per request

I'm pretty sure it hasn't, but apologies if this question has already been asked. And additional apologies if this is just flat out a dumb question but I feel like I'm either completely missing something or have the right idea and just need some backup for my own sanity. I've been implementing WCF Data Services 5.0 in our application and am having no issues with read operations returning entity objects. Unfortunately there is that nasty limitation when it comes to service operations that they can only return primitive types ( See MSDN ). It's very annoying given that it has no problems with

I really like OData (WCF Data Services). In past projects I have coded up so many Web-Services just to allow different ways to read my data. OData gives great flexibility for the clients to have the data as they need it. However, in a discussion today, a co-worker pointed out that how we are doing OData is little more than giving the client application a connection to the database. Here is how we are setting up our WCF Data Service (Note: this is the traditional way) Create an Entity Framework (E)F Data Model of our database Publish that model with WCF Data Services Add Security to the OData

I am developing a WCF DataService that's self-hosted inside a Windows Console Application. I want to activate my service over Https (i.e. SSL) instead of Http. How can I do that? Thanks First Creating a CA Certificate on Windows (use Visual Studio Command Prompt): makecert -sv SignRoot.pvk -cy authority -r signroot.cer -a sha1 -n "CN=Dev Certification Authority" -ss my -sr localmachine Now put the certificate in the "Trusted Root Certification Authority" in Windows Key Store. That can be done through MMC. To do that: Run... -> Type "mmc" -> enter -> choose the "Certificates" console -> Find

ADO.NET Data service is the next generation of data access layer within applications. I have seen a lot of examples using it directly from a UI layer such as Silverlight or Ajax to get data. This is almost as having a two tiered system, with business layer completely removed. Should DAL be accessed by the Business layer, and not directly from UI? ADO.NET Data Services is one more tool to be evaluated in order to move data. .NET RIA Services is another one. Much better I would say. I see ADO.NET Data Services as a low level services to be used by some high level framework. I would not let my UI

I'm using ADO.NET dataservices in a Silverlight application and since the silverlight libraries don't support the ToList() call on the IQueryable I thought it might be possible to create an extension method around this called SilverlightToList(). So in this method I'm calling the BeginExecute method on my context as shown below: var result = context.BeginExecute<T>(currentRequestUri,null,context); result.AsyncWaitHandle.WaitOne(); return context.EndExecute<T>(result).ToList(); The problem is that when I call the WaitOne() method this results in a deadlock. Is this a limitation of ADO.NET