Hot answers tagged


Same happened to me when I tried to send two connections from one provider to one consumer... I tried this, but I obtained the same error: A -> B A -> B To solve this I created a third WebPart between A and B. In my context it had sense, since the new WebPart had a different use than A. So my result was: A -> B A -> C -> B I hope this can help you.


ChannelFactory<IService1> factory = null; BasicHttpBinding binding = new BasicHttpBinding(); binding.Security.Mode = BasicHttpSecurityMode.TransportCredentialOnly; binding.Security.Transport.ClientCredentialType = HttpClientCredentialType.Ntlm; binding.MessageEncoding = WSMessageEncoding.Mtom; EndpointAddress address = new EndpointAddress(newsiteUrl);...


Its not entirely clear what you want to achieve, so maybe if you could clearify the specs for the task? I dont think you can have two filters in one filter web part. Arguably a better design would be to split it up in two filter web parts, but according to this thread, the design for AllowMultipleConnections is that a provider can have more than one ...

Only top voted, non community-wiki answers of a minimum length are eligible