I had a problem when converting my application from VS2003 to VS 2005: Failed to update the Web Service - got an error indicating bad schema format.
This class provides a solution for the .NET 2.0 WSDL - JBOSS problem: When converting a web project from .NET 1.1 to .NET 2.0 and trying to update a Web Service that is connected to a WSDL on a JBOSS service, an error is raised. This util uses WSDL.exe of .NET 1.1 to generate and update the proxy class file.
Using the Code
Execute the application, enter the parameters as described, and click "Execute". The result is a new C# proxy class file, in the destination folder that you entered before execution.
The following code shows how to use WSDL.exe as an external util:
process1 = new System.Diagnostics.Process();
process1.EnableRaisingEvents = false;
process1.StartInfo.FileName = "wsdl.exe";
process1.StartInfo.WorkingDirectory = wsdlCommandPath;
process1.StartInfo.Arguments = "/n:" + nameSpace + @" /out:" +
generatedFileName+ " " + wsdlFilePath;
process1.StartInfo.UseShellExecute = false;
process1.StartInfo.RedirectStandardError = true;
process1.StartInfo.RedirectStandardOutput = true;
string output = process1.StandardOutput.ReadToEnd();
txtOutput.Text = output;
string outputErr = process1.StandardError.ReadToEnd();
if (outputErr != "")
txtError.Text = outputErr;
Points of Interest
I can't help wonder why Microsoft can't make the conversion go smoothly. Why?
My name is Tohar Trabinovitch. I am 32 years old. I am a Software Engineer, graduated on 2002. My expertise is in GUI / Web applications. I am developing in the following technologies for the last 7 years: Web applications using ASP, PHP, JS, AJAX (and before it called AJAX), and .NET (1.1 / 2.0) using C# language (Smart Client / web Services).