Run svcutil.exe specifying metadata address Open the visual studio command prompt or locate the svcutil.exe from the command prompt c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil.exe "http://localhost/managecrm/managecrm.wsdl" /language:C# //use above if you want to generate the proxy in c# c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil.exe "http://localhost/managecrm/managecrm.wsdl" /language:VB //Use above if you want to generate the proxy in VB To Get the helpwith svcuitl.exe use the following command c:\programefiles\microsoft sdks\windows\v6.0A\bin> svcutil The output.config and proxy class will be generated in the "c:\programefiles\microsoft sdks\windows\v6.0A\bin"
XSD ( XSD tool / XSD.exe ) To generate .Net Class file. 1. We can use XSD Tool (Xml Schema Definition Tool) or XSD.exe to generate class files (.cs or .vb ) as per your requirements from Typed Datasets. 2. XSD.exe is the XML Schema Definition tool which generates XML schema or common language runtime classes from XDR, XML, and XSD files. 3. The file locates at C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\XSD.exe OR C:\Program Files\Microsoft Visual Studio .NET 2003\SDK\v1.1\Bin Depends up on your version of .Net. 4. If you are having Express edition of ( V 2.0) then it might possible that you don’t have .Net command prompt option available in Start->Programs , then you have to go command prompt and goto location “C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin” and then type f...
The quality of software depends on many inter-related attributes of the software. Some of the more important ones are: One attribute that I think is very important but I have never seen mentioned before is what I call debugability or how easy it is to track down the cause of a bug. The debugging process consists of three steps: 1. detecting the presence of a bug (aided by verifiability) 2. tracking down the root cause of the bug (aided by debugability) 3. changing the code to fix the (aided by modifiability) Sometimes the second step can be the most time-consuming; this is common in poorly written C code. In C debugability can be greatly improved by such things as assertions (which also improves verifiability, modifiability, reliability, etc). Other environments can greatly improve debugability, such as using Delphi or C# (w/o unsafe code). correctness the extent to which the soft- ware does what it is meant to reliability how often it cr...
Comments