wcf

问题 I am trying to connect to a WCF service someone set up and i'm having trouble, I have no idea what 808:* means in the "Binding Information" for net.tcp site bindings. thanks this is how the bindings are configured in IIS 7 (navigate to IIS, right click on the application hosting the service, click 'edit bindings'). there are two entries: type: http, port: 8000, ip address: *, binding information: (empty) type: net.tcp, port: (empty), ip address: (empty), binding information: 808:* 回答1: I

问题 I'm working on interfacing with a SOAP service that appears to not deal with default namespaces, but works fine with global namespaces and namespace prefixes declared at the SOAP envelope level. The problem is that WCF doesn't create these global namespaces at the root, but rather uses explicit unprefixed default namespaces which the service apparently is choking on. Now I know that this not really WCF's fault - I believe the WCF generated messages are valid XML, but the service chokes on it

问题 Ok, can I vent?? I am so sick and tired of this. I'm working away most of the day and the WCF services are working great. Next time I run my app and make a WCF call, bam! the tcp socket is no longer available. I have searched high and low to solve this and there is no real solution. The only solution I can find is to reboot the machine which is a huge time-waste and burden. Restarting WPA service, net.tcp service, IIS, etc. does not do a thing. Logging off and back on does not fix it. Only a

问题 Ok, can I vent?? I am so sick and tired of this. I'm working away most of the day and the WCF services are working great. Next time I run my app and make a WCF call, bam! the tcp socket is no longer available. I have searched high and low to solve this and there is no real solution. The only solution I can find is to reboot the machine which is a huge time-waste and burden. Restarting WPA service, net.tcp service, IIS, etc. does not do a thing. Logging off and back on does not fix it. Only a

问题 Lately I've been hearing a lot about DTOs and how useful they are but I can't find a good example of using it in ASP.NET context. Let's say I use three tier architecture: Data layer(using Entity Framework) Business Layer(WCF Service) Presentation Layer (MVC 4.0 web application) Where should I convert from the EF Employee object to an EmployeeDTO POCO? Lets say I do the conversion in the Data Access layer but what happens in the WCF service? Should it then be converted to another DataMember

问题 Lately I've been hearing a lot about DTOs and how useful they are but I can't find a good example of using it in ASP.NET context. Let's say I use three tier architecture: Data layer(using Entity Framework) Business Layer(WCF Service) Presentation Layer (MVC 4.0 web application) Where should I convert from the EF Employee object to an EmployeeDTO POCO? Lets say I do the conversion in the Data Access layer but what happens in the WCF service? Should it then be converted to another DataMember

问题 We are trying to come up with a good solution for sharing common libraries, files, executables. We have use case like below Service1 and Service2 are two WCF services developed and maintained by two separate teams and they follow their own release schedules. Common.dll is provided by separate team and they release as per their own schedule. When Common.dll is released beside each Service team testing it, Common team has additional responsibility to approach every service team and their by

问题 My service contract and callback contracts look like this: [ServiceContract(CallbackContract = typeof(IWebshopCallback))] interface IWebshop { [OperationContract] string GetWebshopName (); [OperationContract] string GetProductInfo (Item i); [OperationContract] List<Item> GetProductList (); [OperationContract] bool BuyProduct (string i); [OperationContract] void ConnectNewClient (); } [ServiceContract] interface IWebshopCallback { [OperationContract] void NewClientConnected (int

问题 I want my WCF service to accept and respond to requests in JSON or XML. I thought that WCF was supposed to automatically interpret the response type based on the Accept header that the client specifies. However in my client request I specify the accept header to be application/json but I receive an XML response. This is my service definition: [OperationContract] [WebInvoke(Method = "POST", UriTemplate = "/GetChecks", BodyStyle = WebMessageBodyStyle.Bare)] Check[] GetChecks(MyCustomObj Object)

问题 I want my WCF service to accept and respond to requests in JSON or XML. I thought that WCF was supposed to automatically interpret the response type based on the Accept header that the client specifies. However in my client request I specify the accept header to be application/json but I receive an XML response. This is my service definition: [OperationContract] [WebInvoke(Method = "POST", UriTemplate = "/GetChecks", BodyStyle = WebMessageBodyStyle.Bare)] Check[] GetChecks(MyCustomObj Object)