Invalid contract attribute for IMetadataExchange
Can you delete .SUO (solution Users Option file) file after closing VS? This will reset the cache for XMLEditor component in VS and will fix your problem.
Can you delete .SUO (solution Users Option file) file after closing VS? This will reset the cache for XMLEditor component in VS and will fix your problem.
That’s been a big question surrounding services since their inception. SOA done successfully is SOA planned to the extent you’re talking about. Having said that, I’ve always leaned more toward splitting services out, but using them in a composite manner. That is, several endpoints when you have several contracts, but most of them are only … Read more
To view the message contents you must add a source for System.ServiceModel.MessageLogging in your configuration file. The message tab in the Trace Viewer will show the full message for a particular service call. Here is a sample configuration file: <configuration> … <system.diagnostics> <sources> <source name=”System.ServiceModel” switchValue=”All” propagateActivity=”true”> <listeners> <add name=”traceListener” /> </listeners> </source> <source name=”System.ServiceModel.MessageLogging” … Read more
I finally figured out a solution to this. It’s not what I would have preferred (which would be to return the specific object type, and somehow instruct WCF to use a Json.Net serializer, instead of the DataContractJsonSerializer), but it is working great, and it’s simple and clear. Extending my contrived example using this new solution: … Read more
Nope, the limit is Int64.MaxValue1 which is: 9223372036854775807
This page on MSDN explains WCF Binding Security. http://msdn.microsoft.com/en-us/library/ms729700.aspx The BasicHttpBinding class is primarily used to interoperate with existing Web services, and many of those services are hosted by Internet Information Services (IIS). Consequently, the transport security for this binding is designed for seamless interoperation with IIS sites. This is done by setting the security … Read more
I fixed the problem by turning off validation in my code like this: client.ClientCredentials.ServiceCertificate.Authentication.CertificateValidationMode = System.ServiceModel.Security.X509CertificateValidationMode.None; Where client is an instance of my service reference.
Out of the box WCF will only use the default constructor, you can’t use parameterised constructors. You have to do a bit of extra work to make WCF call parameterised constructors. You could try this: How do I pass values to the constructor on my wcf service?
Check here: http://developers.de/blogs/damir_dobric/archive/2006/07/31/890.aspx and http://msdn.microsoft.com/en-us/library/ff648505.aspx Transport seems to require HTTPS to encrypt credentials and throws an exception if there is no SSL. TransportCredentialOnly will send the credentials in plain text and unencrypted and is recommended for testing ONLY! Good Luck!!