The question does not seem to make any sense. There is no such thing as "addressing WSDL.exe". This is nothing but some development tool, an application use to generate code for XML Web services and clients:
https://msdn.microsoft.com/en-us/library/7h3ystb6%28v=vs.100%29.aspx[
^].
I cannot understand how anyone can have problems running a (console-only) application if the application itself is available. However, some of such applications can be guaranteed to run if you run it in a specially setup environment, which is done for you with Visual Studio installation. Each version of Visual Studio provides a set of
shortcuts under the directory prescribed in the system menu under the name "Visual Studio Tools", and the link will have the name like "VS* * Command Prompt". If you click on such link, it will execute a standard Windows command-line box with all paths and other definitions already prescribed, so you can run all applications directly, using simple file names, such as "WSDL.EXE", with parameter or not.
If you simply execute CMD.EXE in some random directory (or command-line text box in any other application providing command-line input), you will see, quite naturally. the message
'wsdl.exe' is not recognized as an internal or external command, operable program or batch file.
No wonder, the command-line interpreter won't know where to find the file named like that. Some other definitions can also be required. Therefore, use VS Command Prompt.
You don't have to understand what environment definitions are required and missing, but if you are curious, or if you want to write your own batch file for running your tools, you can easily find it out. Locate the "* Command prompt" link, activate the context menu to see Properties, and then locate the Shortcut Target (Tab: "Shortcut", control label: "Target"). It will be some batch file. Locate it, open it in a text editor and see what it does.
—SA
Submit an article or tip