wcf-data-services

I am creating an OData service with WCF Data Services using an EDMX. How can I create a computed property for an entity type, so that its value gets computed in the service (C#) and does not come from the database? The value of this property is based on the value of other properties, which are mapped to fields in the database. If you are exposing your EDMX file directly, using the default Entity Framework Provider for Data Services, something like this: public class MyService: DataService<MyEntities> { Then unfortunately you can't expose any 'new' properties that aren't in the underlying

I used following jQuery to insert data via Data Service. Event though I got status-response 201 and the data is successfully inserted into my database, the system still regard it as an error and gives me "failed" alert? What am I missing here? $.ajax({ type: "POST", url: "http://localhost:49223/Form/WebDataService.svc/XMLForm(guid'1eaef3a0-d6df-45bf-a8f6-3e7292c0d77e')/XMLRecord/", data: JSON.stringify(record), contentType: "application/json; charset=utf-8", dataType: "json", success: function() { alert("Success"); }, error: function(xhr) { alert("fail"); } }); UPDATE: Debug Message from Fire

I'm trying to manually build a WCF Data Service using a POCO data model and I cannot figure out how to properly expose enum values. Assuming a simple model like: public class Order { public int ID {get; set;} public string Description {get; set;} public OrderStatus Status {get; set;} } public enum OrderStatus { New, InProcess, Complete } How do you expose the valuable information in the OrderStatus property via the OData WCF Data Service? If you do nothing, the Data Service generates a runtime error (enum is invalid property). The only answer I've seen that at least resolves the error is to

This sounds rather simple (and maybe I'm missing the obvious here) but I can't find a solution. I know I can query an entity and return one, or many direct child entities doing this: var query = from c in Service.Clients.Expand("Addresses,Comments,PhoneNumbers").. What I would like to be able to do is do the same with 3 levels (Children of child), lets say "Country->Province->City" or "Brand->Family->Model" I tried to expand all entities, but it fails var query = from c in Service.Brands.Expand("Families,Models").. //fails, //which even makes some sense, since Models is a Child of Family, not

I'm trying to use WCF Data Services and a little confused what library should I reference to interact with WCF Data Services: Microsoft.Data.Services.Client.dll or System.Data.Services.Client.dll . What is the difference between them? In which case should I use each of them? When trying to add references to both of them I get a compiler error: The type 'System.Data.Services.Client.DataServiceContext' exists in both 'e:\Program Files\WCF Data Services Mar 2011 CTP2\bin.NETFramework\Microsoft.Data.Services.Client.dll' and 'e:\Program Files\Reference Assemblies\Microsoft\Framework.NETFramework\v4

I'm using EF 6.1.0 and was creating a WCF Service. First I created a Class Library containing my entities, Mappers and Context for initializing EF. I've also created a class containing an instantiation of the context and have this code: public IQueryable<[Entity]> GetAll() { return context.[Entity].AsQueryable(); } On the otherhand, I've created a WCF Service on the same project and Calls the function GetAll() in the.svc file like this: public List<[Entity]> GetList() { [iObject] repository = new [Object](new Context()); return repository.GetAll().ToList(); } The project is building. I even

I'm currently experiencing an issue trying to send large data using WCF self hosted service (no IIS). Transferring 500MB using streaming results with my service crashing with System.OutOfMemoryException. Is it possible at all to transfer such amount of data? Here is my WCF configuration: <system.serviceModel> <services> <service name="CIService" behaviorConfiguration="CIBehavior"> <host> <baseAddresses> <add baseAddress="net.tcp://localhost:6547/CIService/CIService.svc" /> </baseAddresses> </host> <endpoint binding="netTcpBinding" bindingConfiguration="netTcpBindingConfig"