More WCF woes... :)
All my workflows implement the same 3 methods. After a lot of copy and paste, I decided to make them inherit from the same interface:
<
Why don't you specify a name for your contract in the ServiceContract attribute:
[
ServiceContract
(
Namespace = "http://schema.company.com/messages/",
Name="MyBasicContract"
)
]
If you don't explicitlly specify a name, it will default to the qualified name of your interface in "that weird syntax that .NET uses".
"that weird syntax that .NET uses" is actually the type name at runtime for a generic type bound to specific types. Typename`n[[Type],...] where n denotes the number of type arguments contained in your generic type.
How does your endpoint configuration then look like?
You must use the standard way of defining generic types in configuration file if you want to use a service contract like IBasicContract
It is written in the configuration file like this: IBasicContract`2[TRequest,TResponse]
I also replied on my blog (www.lybecker.com/blog/) as you posted the question their too.
:-) Anders Lybecker