of version 2.0.0 of XML-RPC.NET the distribution contains two assemblies named CookComputing.XmlRpc.dll and CookComputing.XmlRpcV2.dll. The CookComputing.XmlRpc assembly located in the bin1_0 directory is built with the .NET 1.0 compiler (version 1.0.3705). This allows it to used with all released versions of the .NET runtime and with code built for all those versions. The version should be used where backwards compatibility is required. The CookComputing.

The final versions of the 1.0 SDK and runtime were made publicly available around 6pm PST on 15-Jan-2002. At the same time, the final version of Visual Studio.NET was made available to MSDN subscribers. NET 2.0 was released to MSDN subscribers in late October 2005, and was officially launched in early November. See similar questions...

I am running Windows Vista, and TracePlus? cannot intercept applications that I launch from the Start menu or the Desktop See similar questions...

XML-RPC.NET is used as a single assembly which contains both client and server classes. When used by another program, installation is simply a matter of ensuring that the assembly is in the same directory as the program using it or referred to using the program's config file if in another directory. There are two builds of the assembly: CookComputing.XmlRpc.dll which runs on all versions of .NET and CookComputing.XmlRpcV2.dll which runs on .NET 2.0 onwards. See similar questions...

XML-RPC.NET is built with a strong name and so can be added to the Global Assembly Cache (GAC). To do this use the gacutil utility: gacutil /i CookComputing.XmlRpcV2.dll Alternatively the dll can be dragged and dropped into the winnt\assembly directory using Windows Explorer. See similar questions...

When compiling code which uses any of the classes in the XML-RPC.NET assembly, a reference to the assembly must be specified. In Visual Studio .NET this is is achieved by using the References dialog which is invoked from the References item in the Solution Explorer. If compiling from the command line, the XmlRpc assembly is referenced like this: csc /r:CookComputing.XmlRpcV2.dll myprogram.cs See similar questions...

XML-RPC.NET is fully Common Language Specification (CLS) compliant. This means that it can be used from any .NET language which is also CLS compliant, for example C#, VB.NET, or Managed Extensions for C++. See similar questions...

XML-RPC.NET services under IIS run within the aspnet_wp.exe process and so must be debugged by attaching a debugger to this process. From the Tools menu, choose Debug Processes. Check the Show system processes checkbox, if it is not checked (this may not be necessary, depending on the account aspnet_wp.exe is running under). Check Common Language Runtime on the Attach to Process dialog which then appears and click OK. (It is ok to leave Native checked. See similar questions...

The Network Development and MARC Standards Office has developed a framework for working with MARC data in a XML environment. This framework is intended to be flexible and extensible, allowing users to work with MARC data in ways that meet their specific needs. The framework contains many components such as schemas, stylesheets, and software tools developed and maintained by the Library of Congress. Conversion utilities between MARC (ISO 2709) and MARCXML are also available. Please see www.loc. See similar questions...

If your code makes a call on a proxy and an XmlRpcIllFormedXmlException is thrown with the message "Response from server does not contain valid XML." it means that the XML-RPC response from the server cannot be parsed as a valid XML document (parsing is performed by the .NET XmlDocument class). It is not a problem with the client. See section 5.1 on how to investigate what the server is sending across the network. Section 2. See similar questions...

Yes - as long as the web server supports ASP.NET. This is not as implausible as it might sound because it is fairly easy to host ASP.NET using the .NET implementation of System.Web.Hosting. An example of this is the Cassini Web Server implemented by the ASP.NET team. One point worth mentioning when running Cassini is that assemblies by default must be placed in a directory called bin under the virtual root. For example, if the URL of the service is http://localhost/xmlrpc/math. See similar questions...

Use the sn.exe tool to extract the public key token from the assembly: sn -T cookcomputing.xmlrpcV2.dll The token should be the same as this if the assembly was built using the Cook Computing key file: a7d6e17aa302004d See similar questions...

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be incl. See similar questions...

XML-RPC.NET represents an XML-RPC endpoint as a .NET interface whose methods map onto the corresponding XML-RPC methods. For example: using CookComputing.XmlRpc; public struct SumAndDiffValue { public int sum; public int difference; } [XmlRpcUrl("http://www.cookcomputing.com/sumAndDiff.rem")] public interface ISumAndDiff { [XmlRpcMethod] SumAndDiffValue SumAndDifference(int x, int y); } A server implementation implements these methods. See similar questions...

The base class for implementing all types of XML-RPC server is XmlRpcServerProtocol. This implements the Introspection API and so all XML-RPC.NET endpoints automatically expose this API. See similar questions...

Our components are written for Version 1.1 of the .NET Framework. They will also work with Version 2.0. They are not compatible with the Compact Framework. See similar questions...

Both .NET v1.0 and .NET v1.1 with a future FixPack to update to support .NET v2.0 which is (at the time of writing) still in development. Version 3 of HotHTML does not provide any WYSIWYG editing features, nor support ASP.NET Web Forms editing visually(only code). See similar questions...