Reputation: 1
I am attempting to replace a WSE service with the WCF equivalent where the WSDL is provided externally.
First, I used svcutil and wsdl to generate all the service and client classes (ATP, I'm only concerned with the service implementation.) I generated an empty WCF Service Library project and replaced/renamed the IService1.cs
with a class named for the interface ServiceContractAttribute
generated. I then renamed the implementation class Service1.cs
with the name of the implementation-class JINDEXWcfListener.cs
. I removed the generated code from this class and created class definition JINDEXWcfListener:[interface name]
.
The tool auto-generated the implementation of the interface. I used the single method adorned with [OperationContractAttribute]
to put my local implementation code. I modified the default app.config
generated to adjust the contract and service names as required.
When I start debug, I can see that the service is starting in the WTC. However, when the single operation is exposed, the is a red dot with a yellow question mark in front of the operation name. When I RC on the op name, I get "This operation is not supported in WCF Test client" with no additional information. What is wrong?
Upvotes: 0
Views: 901
Reputation: 533
WCFTestClient has quite a few limitations. I have fought "problems" for several hours that later turned out to be just WCFTestClient problems. Complex objects can give you a lot of grief, also any custom lists, etc such as a custom implementation of the IList interface. Try out WcfStorm. I think they have a free version and a trial version.
Upvotes: 1