wcf-binding

问题 I'm trying to use WCF named pipes in a web site, and it's failing with errors: There was no endpoint listening at net.pipe://localhost/mypipename that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. and the InnerException: The pipe name could not be obtained for net.pipe://localhost/mypipename. and there is another inner exception giving an access denied message. My web site is using impersonation, and

问题 I am trying to use the WCF streaming with Message Contracts, because I need additional parameters beside the stream itself. Basically I am creating a file upload and download service, with some additional logic on top. Unfortunately, when I try to hit the service from the browser to check that everything is all right, I get the following error: Server Error in '/' Application. Operation 'UploadFile' in contract 'IFileTransferService' uses a MessageContract that has SOAP headers. SOAP headers

问题 I spent a lot of time figuring out how to configure my WCF services so that they would work for https in the production environment. Basically, I needed to do this: <behaviors> <serviceBehaviors> <behavior name="MyServiceBehavior"> <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" /> <serviceDebug includeExceptionDetailInFaults="true" /> </behavior> </serviceBehaviors> </behaviors> <serviceHostingEnvironment multipleSiteBindingsEnabled="true" aspNetCompatibilityEnabled="true" />

问题 This question already has an answer here : BasicHttpBinding vs WsHttpBinding vs WebHttpBinding (1 answer) Closed 3 years ago . In a WCF endpoint, what is the difference between basicHttpBinding and wsHttpBinding? When should each be used? 回答1: Ton of material on that out there - just google for "WCF basicHttpBinding wsHttpBinding". You'll find amongst others: WCF : BasicHttpBinding compared to WSHttpBinding at SOAP packet level. Difference between BasicHttpBinding and WsHttpBinding and many,

问题 I need to create a WCF service that is hosted in IIS, uses http transport and hold state in the server’s memory. While I’m aware that stateful services aren't a good idea, this last constrain is necessary to make the service work with a legacy client. My first thought was to asp.net’s session to store the values. I activated the asp.net compatibility mode in my service, which gave me access to the HttpContext, but values that were placed in the session object were not being persisted in

问题 I am trying to access my WCF service on a server from my client console application for testing. I am getting the following error: The caller was not authenticated by the service I am using wsHttpBinding . I'm not sure what kind of authentication the service is expecting? <behaviors> <serviceBehaviors> <behavior name="MyTrakerService.MyTrakerServiceBehavior"> <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment --

问题 How do the timeouts work in WCF? I know for example that you can configure sendTimeout and receiveTimeout for a clients binding. But how do they work? MSDN describes sendTimeout as: A TimeSpan value that specifies the interval of time provided for a send operation to complete. This value should be greater than or equal to Zero. The default is 00:01:00. What are send operations/receive operations? 回答1: Client side: SendTimeout is used to initialize the OperationTimeout, which governs the whole

问题 In WCF there are several different types of HTTP based bindings: BasicHttpBinding WsHttpBinding WebHttpBinding What are the differences among these 3? In particular what are the differences in terms of features / performance and compatability? 回答1: You're comparing apples to oranges here: webHttpBinding is the REST-style binding, where you basically just hit a URL and get back a truckload of XML or JSON from the web service basicHttpBinding and wsHttpBinding are two SOAP-based bindings which

问题 I'm trying to connect an application (the client) to an exposed WCF service, but not through the application configuration file, but in code. How should I go about doing this? 回答1: You'll have to use the ChannelFactory class. Here's an example: var myBinding = new BasicHttpBinding(); var myEndpoint = new EndpointAddress("http://localhost/myservice"); using (var myChannelFactory = new ChannelFactory<IMyService>(myBinding, myEndpoint)) { IMyService client = null; try { client = myChannelFactory

问题 I've added a proxy to a webservice to a VS2008/.NET 3.5 solution. When constructing the client .NET throws this error: Could not find default endpoint element that references contract 'IMySOAPWebService' in the ServiceModel client configuration section. This might be because no configuaration file was found for your application or because no endpoint element matching this contract could be found in the client element. Searching for this error tells me to use the full namespace in the contract