Search Results for "can"

...The main purpose of RestSharp is to make synchronous and asynchronous calls to remote resources over HTTP. As the name suggests, the main audience of RestSharp are developers who use REST APIs. However, RestSharp can call any API over HTTP (but not HTTP/2), as long as you have the resource URI and request parameters that you want to send comply with W3C HTTP standards. RestSharp can take care of serializing the request body to JSON or XML and deserialize the response. It can also form a valid request URI based on different parameter kinds.

...For example: _________________________________________ ObjectXmlNavigator nav = new ObjectXmlNavigator("myObject", MyObject); XslTransform xslTrans = new XslTransform(); xslTrans.Transform(nav, null, objStream); _________________________________________ Using the ObjectXmlNavigator object you can now access the properties of MyObject in your XSLT. Only properties (or properties of properties) that your reference in your XSLT will be 'converted' to XML, hence the 'Lazy' serializer.

FFEntityFramework is an Object-Relational Mapping Framework (O-R Mapping / Object Persistence) for .NET with built-in features like Xml-Serialization, Model-View-Controller-Framework or UndoManagement ... All these Components use the same Meta-Base which can be definied via Attributes (Annotations) on your Business-Classes. Nevertheless differences between Xml- and Db-Serialization can be made via an enum MetaUsage (Database, Xml, Internal …). For Example you can define a Key-Column which is only used for Db-Serialization and excluded for Xml-Serialization. The same can be done with References, Delegations &c. ...

Web Objects in XML (serializer) provides easy XML serialization of Java and C# objects. Objects are serialized to a file in a standard XML format. They can then be de-serialized either to Java or C#.