Skip to main content

Generating a WCF Client from Service Metadata

This topic describes how to use the various switches in Svcutil.exe to generate clients from metadata documents.
Metadata documents can be on a durable storage or be retrieved online. Online retrieval follows either the WS-MetadataExchange protocol or the Microsoft Discovery (DISCO) protocol. Svcutil.exe issues the following metadata requests simultaneously to retrieve metadata:
  • WS-MetadataExchange (MEX) request to the supplied address.
  • MEX request to the supplied address with /mex appended.
  • DISCO request (using the DiscoveryClientProtocol from ASP.NET Web services) to the supplied address.
Svcutil.exe generates the client based on the Web Services Description Language (WSDL) or policy file received from the service. The user principal name (UPN) is generated by concatenating the user name with "@" and then adding a fully-qualified domain name (FQDN). However, for users who registered on Active Directory, this format is not valid and the UPN that the tool generates causes a failure in the Kerberos authentication with the following error message: The logon attempt failed. To resolve this problem, manually fix the client file that the tool generated.
svcutil.exe [/t:code]  <metadataDocumentPath>* | <url>* | <epr>

Option
Description
/reference:<file path>
References types in the specified assembly. When generating clients, use this option to specify assemblies that might contain types that represent the metadata being imported.
Short form: /r
/excludeType:<type>
Specifies a fully-qualified or assembly-qualified type name to be excluded from referenced contract types.
Short form: /et

Option
Description
/serializer:Auto
Automatically selects the serializer. This uses the DataContract serializer. If this fails, the XmlSerializer is used.
Short Form: /ser:Auto
/serializer:DataContractSerializer
Generates data types that use the DataContract serializer for serialization and deserialization.
Short form: /ser:DataContractSerializer
/serializer:XmlSerializer
Generates data types that use the XmlSerializer for serialization and deserialization.
Short form: /ser:XmlSerializer
/importXmlTypes
Configures the DataContract serializer to import non-DataContract types as IXmlSerializable types.
Short form: /ixt
/dataContractOnly
Generates code for DataContract types only. ServiceContract types are generated.
You should specify only local metadata files for this option.
Short form: /dconly

Option
Description
/language:<language>
Specifies the programming language to use for code generation. Provide either a language name registered in the Machine.config file or the fully-qualified name of a class that inherits from CodeDomProvider.
Values: c#, cs, csharp, vb, vbs, visualbasic, vbscript, javascript, c++, mc, cpp
Default: csharp
Short form: /l
For more information, see CodeDomProvider Class.

Option
Description
/namespace:<string,string>
Specifies a mapping from a WSDL or XML Schema targetNamespace to a common language runtime (CLR) namespace. Using a wildcard (*) for the targetNamespace maps all targetNamespaces without an explicit mapping to that CLR namespace.
To make sure that the message contract name does not collide with the operation name, either qualify the type reference with double colons (::) or make sure the names are unique.
Default: Derived from the target namespace of the schema document for DataContracts. The default namespace is used for all other generated types.
Short form: /n

Option
Description
/enableDataBinding
Implements the INotifyPropertyChanged interface on all DataContract types to enable data binding.
Short form: /edb

Option
Description
/config:<configFile>
Specifies the file name for the generated configuration file.
Default: output.config
/mergeConfig
Merges the generated configuration into an existing file, instead of overwriting the existing file.
/noConfig
Do not generate configuration files.


Labels:

Comments

Post a Comment

Popular posts from this blog

C# Generic class to parse value - "GenericConverter"

    public class GenericConverter     {         public static T Parse<T>(string sourceValue) where T : IConvertible         {             return (T)Convert.ChangeType(sourceValue, typeof(T));         }         public static T Parse<T>(string sourceValue, IFormatProvider provider) where T : IConvertible         {             return (T)Convert.ChangeType(sourceValue, typeof(T), provider);         }     }     public static class TConverter     {         public static T ChangeType<T>(object value)         {             return (T)ChangeType(typeof(T), value);         }         public static object ChangeType(Type t, object value)         {             TypeConverter tc = TypeDescriptor.GetConverter(t);             return tc.ConvertFrom(value);         }         public static void RegisterTypeConverter<T, TC>() where TC : TypeConverter         {             TypeDescriptor.AddAttributes(typeof(T), new TypeConverterAttribute(typeof(TC)));         }     } ----------------
Post a Comment
Read more

How to create a countdown timer in jquery

Create a countdown timer in jQuery First we need to include the jQuery library file to the HTML page to perform this task. To do that we need to understand that what exactly a jQuery library fie is ? JQuery library file is the library of JavaScript, which means this file contains the predefined functions of jQuery. We just need to call these functions to perform the task. jQuery functions reduces the lines of code and makes our task easy. As this jQuery library file contains the javascript functions so we need to call the function within <script> </script> tag. Now after including the file, we need to define a variable which will store that for how long you want the timer on the page(c=60) and now the time you set needs to be changed in hours , minutes and seconds using the code “ var hours = parseInt( time / 3600 ) % ;var minutes = parseInt( time / 60 ) % 60; var seconds = time % 60;” Now we need to put the condition if timer got finished (if (t
1 comment
Read more

Validate credit card number with Mod 10 algorithm in C#

Introduction All you know what information contains in your NIC number. But do you know what information contains in the Credit Card Number? Following article provides brief details about what information contain in your credit card and demonstrates to how to validate credit card number using mod 10 (Luhn) algorithms with C#. Background  Card Length   Typically, credit card numbers are all numeric and the length of the credit card number is between 12 digits to 19 digits.  14, 15, 16 digits – Diners Club 15 digits – American Express 13, 16 digits – Visa 16 digits - MasterCard   For more information please refer  http://en.wikipedia.org/wiki/Bank_card_number . Hidden information  Major Industry Identifier (MII)   The first digit of the credit card number is the Major Industry Identifier (MII). It designates the category of the entry which issued the card.     1 and 2 – Airlines  3 – Travel 4 and 5 – Banking and Financial 6 – Merchandising and Banking/Fina
1 comment
Read more