Files
mono/mcs/class/System.ServiceModel/Test
Atsushi Eno 0c7a1a1f5c Fix the issue that callback contract often gets confused by picking unexpected contract type.
The problem is that DispatchRuntime.Type is a service implementation type
that could implement two or more contract interfaces, and it was in random
order how ServiceProxyGenerator picks up the contract type. Now it looks
for correct contract type instead of the service type by exactly looking
for the target contract in the endpoint (dispatcher).
2010-09-29 16:41:59 +09:00
..
2010-07-25 20:17:39 +05:30
2010-07-25 20:17:39 +05:30
2010-07-25 20:17:39 +05:30
2010-07-25 20:17:39 +05:30

How to add a new test WCF Client/Server test:



1. In directory FeatureBased/Features.Contracts add a new contract and implementation class. It is best to copy an existing one and modify it.

2. In directory FeatureBased/Features.Serialization add a new test class. Again copy from a different test class, but remove all members. 

   Maintain the inheritance from TestFixtureBase<clientProxy, ServerImplementation, ServerContract>.  However, since you don't have a client

   proxy yet, use 'object' instead.

3. Run the WCFServers executable. This will start the server so it is now running.

4. In command prompt, in directory  Test\FeatureBased\Features.Client run "svcutil.exe <endpointbase>/<serverclassname>_wsdl /n:*,Proxy.MonoTests.Features.Client" e.g.

   svcutil http://localhost:9999/ExitProcessHelperServer_wsdl /n:*,Proxy.MonoTests.Features.Client

5. Include the file in the project

6. In the test class created in step #2, modify the name of the client proxy class to the name of the generated class.