.NET WebService Studio and WCF

Here's an example:

You have created a service.

To test this service, you will need to create a client and use it to call the service. You can do this using the svcutil.exe tool from the command line with the following syntax:

svcutil.exe http://<server>.com:4999/MartService.svc?wsdl 
This will generate a configuration file and a code file that contains the client class. Add the two files to your client application and use the generated client class to call the Service. For example:
 
C#
class Test
{
 static void Main()
 {
 MartServiceClient client = new MartServiceClient();
 // Use the 'client' variable to call operations on the service.
 // Always close the client.
 client.Close();
 }
}

 
Visual Basic
Class Test
 Shared Sub Main()
 Dim client MartServiceClient = New MartServiceClient()
 ' Use the 'client' variable to call operations on the service.
 ' Always close the client.
 client.Close()
 End Sub
End Class
 
gn_ctax at 2007-10-3 > 

Does this mean that the web service piece Microsoft's latest and greatest interoperability standard (WCF) does not meet compliance with WS-I standards?

Say it ain't so!

That's good to know, but why doesn't WebService Studio work with it anymore? Was it not written to interpret WSDLs based on standards then? Incidentally SOAP UI worked out of the box with .NET 2.0 Web Services but have the same problem as WebService Studio for WCF Web Services.