This is simply because WCF uses Lax Versioning .
In many other scenarios, the service developer may make the assumption that adding a new, optional member to the data contract will not violate existing customers. This requires the service developer to investigate whether existing clients do not perform schema validation and that they ignore unknown data members. In these scenarios, it is possible to use the data transfer capabilities to add new members in the wrong way. The service developer can make this assumption by using the assurance that contract functions with version control data already exist for the first version of the service.
Many web service platforms, including WCF and XML web services, do not perform default schema validation and therefore allow additional elements that are not described in wsdl. This is not the case for every platform, and several java clients perform strict schema validation.
Try to remove the parameter now, you will not get the same results.
source share