wcf-data-services

I'd like to know if you can recommend any advanced ADO.NET libraries for working with databases. I've discovered that LINQ-to-Entities is great for pulling data out of databases, but not at all useful for inserting data into databases. Its missing functionality like fast bulk insert, culling of duplicates, and most of the advanced functionality you can achieve with pure SQL. So: can you recommend some ADO.NET libraries that offer the sorts of advanced functionality that LINQ-to-Entities is missing? The ADO.net SqlBulkCopy class enables quick, mass upload of records into a table: DataTable dt =

I have created a web service in WCF which returns more than 54000 data-rows with 10 data in each row. I have used the wsHttpBinding for communication. The service works well with less data (i.e. 2000 rows) but it bombs out when attempting to send large record set with 50000+ rows(~2MB). The exception message is like this An error occurred while receiving the HTTP response to http://localhost:9002/MyService.svc . This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the

I am trying create a WCF Data Services ServiceOperation that does grouping on the server side and then sends the data down to the client. When I try to call it (or even connect to the service) I get an error. It says that it can't construct an interface. The only interface I am using is IGrouping. What is a/the actual class for this interface? Update: I checked the type while debugging a sample app and it told me it was: System.Linq.Lookup<TKey,TElement>.Grouping But what assembly is it in? Several types in the BCL implement IGrouping , however they are all internal and cannot be accessed

There are many reasons create a RESTful WCF server (it is easy) and even better if you can avoid ASP and it's security box (if all you are doing is simple requests to return information). See: http://msdn.microsoft.com/en-us/library/ms750530.aspx on how to do this. What I found is that handling AJAX (JQUERY) GET requests is easy. But dealing with JSON in a POST is tricky. Here is an example of a simple GET request contract: [OperationContract] [WebGet(ResponseFormat = WebMessageFormat.Json)] String Version(); And the implementaion is here (which returns a JSON) public partial class