.net - Portable / Interoperable WCF Contracts -


I was thinking that some good suggestions for creating a WCF contract with anyone for the web / DOS and Don was not - the difference between services, in terms of both old Microsoft web service technologies (such as WSE) and non-Microsoft technologies such as Java Call WCF Web Services

For example: As the date time When Agr are no special rules? How about dictionary and hashtables? What problems can you get with different bins?

WCF date time crisis

Regarding your date question, you are concerned It is just a link to many people who have gone through DTC time through WCF, which is complaining about the difficulties ...

About the type of similarity

< P> According to section 3.1.3 of the book named Juwel Lavi of Programming WCF Services, Second Edition ..

WCF provides the underlying data contract for primitive types because there is an industry standard for those types of schemas.

He also states that regarding the use of custom types in the form of parameters on operation agreement methods, I believe that this method also applies to the return type.

To be able to use a custom type as an operation parameter, there are two requirements: first, the type must be sorted, and the second, both the client and the service A local definition is required which results in the same data schema.

You may also want to check section F.4. Data contracts, which are part of their WCF coding standard. Bullet # 9 applies to your question ...

Do not pass the .NET-specific type, such as the type of operating parameters.

Install bindings expectations

Binding based on WSHttpBindingBase (Search for Refractor.NET for its four derivations) are going to be most interoperable, because they are for interoperability Are designed.

Book Recommendation

I highly recommend the book of Juwel:


Comments