XmlSerializer

151 of 174 | NDS Licenses EXPWAY BinXML Software for Integration into Its Broadcast Solutions - Integration Will Offer Broadcasters Bandwidth Efficient Solution for Data Intensive ApplicationsLONDON--Dec. 6, 2004--NDS Group plc (NASDAQ/Euronext Brussels:NNDS), a News Corporation company and a leading provider of technology solutions for digital pay TV, today announced that it has licensed EXPWAY`s Binary XML solution, BinXML(TM), as part of its ongoing commitment to provide state of the art technology solutions to operators and broadcasters. NDS plans to integrate and deploy BinXML(TM) into its range of head-end systems and receiver middleware solutions....

152 of 174 | Simple, Fast, no-Loss binary XML - Fast Infoset - What can you do if you would want to use XML but you are having performance problems Binary encodings have been proposed and investigated for a while but they have yet to gain real adoption. Here is a proposed standard that delivers substantial performance benefits without losing the benefits of XML. Think of it as an improved GZIPed XML... ...

153 of 174 | Binary XML proponents stir the waters - The XML Binary Characterization Working Group made a pitch at last week`s XML Conference & Exhibition 2004, recommending that the W3C specify a single binary XML format. That`s got a lot of text XML vendors and users wringing their hands....

154 of 174 | A new code generation API - I find System.Reflection.Emit too low level for some kind of uses. If you are writing a compiler, SRE is just perfect, since you need to have full control of the IL being generated. However, if you are writing, guess what, an xml serializer, SRE is not so useful. An xml serializer needs to generate code for writing and reading the contents of an object, and this code is not simple (it will include type conversions, method calls, loops, etc.). For complex types the IL code may be very long, and debugging this code if something goes wrong would be really hard. The existing XmlSerializer does not generate IL, instead it generates C# code and compiles it using the C# compiler. This solution h......

155 of 174 | Boost XmlSerializer usability and performance by using strongly-typed serializers - The XmlSerializer has a farily well-known problem: the first time you use it, it will generate a class to read instances of the received type, compile it, and then load it. Of course, this can take considerable time, directly related to the complexity of the type and all its members and member types. Unlike common wisdom, this is something that can be avoided and I have explained (albeit rather confusingly) in a previous post. The usage was not great, though, as it was a command-line tool: ouch! So, the Mvp.Xml project debuts with a new package: Mvp.Xml.Design. Now, in order to get a design-time version of a custom XmlSerializer for a type, you just assign the Mvp.Xml.XGen (renamed from t......

156 of 174 | Hindsight is 20/20: Three Things XML Got Wrong - Derek Denny-Brown, the dev lead for both MSXML & System.Xml, who's been involved with XML before it even had a name has finally started a blog. Derek's first XML-related post is Where XML goes astray... which points out three features of XML that turn out to have caused significant problems for users and implementers of XML technologies. He writes First, some background: XML was originally designed as an evolution of SGML, a simplification that mostly matched a lot of then existing common usage patterns. Most of its creators saw XML and evolving and expanding the role of SGML, namely text markup. XML was primarily intended to support taking a stream of text ......

157 of 174 | Hindsight is 20/20: Three Things XML Got Wrong - Derek Denny-Brown, the dev lead for both MSXML & System.Xml, who`s been involved with XML before it even had a name has finally started a blog. Derek`s first XML-related post is Where XML goes astray... which points out three features of XML that turn out to have caused significant problems for users and implementers of XML technologies. He writes First, some background: XML was originally designed as an evolution of SGML, a simplification that mostly matched a lot of then existing common usage patterns. Most of its creators saw XML and evolving and expanding the role of SGML, namely text markup. XML was primarily intended to support taking a stream of text intended to be interpreted as a......

158 of 174 | PocketSOAP 1.5 released ! - Its been a long time coming but the final release of PocketSOAP v1.5 is now available, new features and improvements includeSOAP 1.2 support.Reduced memory footprint during serialization & messaging sending/receiving.Streaming parsing of the response soap envelope.Support for gzip in addition to deflate compression.Improved performance of base64 handling.upgraded to zlib 1.2.1 for improved compression performance.zlib & expat dependencies are now statically linked for easier deployment and less dll hell.A bunch of bug fixes....

159 of 174 | The XML Litmus Test: Understanding When and Why to Use XML - I just finished writing last month`s Extreme XML column* entitled The XML Litmus Test: Understanding When and Why to Use XML. The article is a more formal write up from my weblog post The XML Litmus Test expanded to contain examples of appropriate and inappropriate uses of XML as well as with some of the criteria for choosing XML fleshed out. Below is an excerpt from the article which contains the core bits that I hope everyone who reads it remembers   XML is the appropriate tool for the job if the following criteria are satisfied by choosing XML as the data representation format for a given application. 1.      there is a need to interoperate across ......

160 of 174 | Calling a .NET Assembly from Orchestration with Schema Types - There I was today pointing at a customer at a past blog entry on this topic when I realized Id never got around to posting it, Doh!  Apologies for sitting on this for the last few months! I was running some BizTalk training earlier this year and got talking about how you can pass Messages from BizTalk to a .NET component.  The typical approach is to define a parameter of XLANGMessage (Which is BizTalks in-memory representation of a message) and you can then natively pass the message from BizTalk to your .NET component. You can then crack that XLANGMessage inside your .NET component and retrieve the underling Message body; as with everything inside BizTalk you can do this in a few ways!   ......

161 of 174 | Calling a .NET Assembly from Orchestration with Schema Types - There I was today pointing at a customer at a past blog entry on this topic when I realized Id never got around to posting it, Doh!  Apologies for sitting on this for the last few months! I was running some BizTalk training earlier this year and got talking about how you can pass Messages from BizTalk to a .NET component.  The typical approach is to define a parameter of XLANGMessage (Which is BizTalks in-memory representation of a message) and you can then natively pass the message from BizTalk to your .NET component. You can then crack that XLANGMessage inside your .NET component and retrieve the underling Message body; as with everything inside BizTalk you can do this in a few ways!   ......

162 of 174 | Base 64 Format Conversion - Recently, I was working with an InfoPath solutions prototype. The idea behind the solution was that a user would be taking a digital photo (JPEG). As they downloaded the pictures to their local machines, they would be able to include these camera shots into an InfoPath form that contained additional descriptive fields. By default, InfoPath takes these types of binaries and converts them into a Base 64 format. Once converted this data is then saved to an XML file. One requirement of the solution was to convert this data back to its original JPEG format once it was saved to the server, so that it could be displayed or saved. For an example application, I created a simple data source based o......

163 of 174 | Chris Anderson: Developers Hate XML - According to the current version of the Chris Sells XML DevCon page (don`t bother bookmarking it, Chris Sells doesn`t believe in permalinks so all the content on that page is transient) I noticed that Chris Anderson is presenting the following Developers Hate XML Chris Anderson While everyone is currently infatuated with XML, developers are constantly doing battle with trying to rationalize and leverage XML in their applications. Ill talk about having to balance correct XML-isms vs. usability in XAML, about the preponderance of XML reader/writer/DOM/serialization APIs, and about how all of this throws you into a horrible programming experience of loosely......

164 of 174 | Things I`m doing - After all, there aren`t many new things regarding Web Services in .NET 2.0: support for Soap 1.2, a basic profile conformance checker, some new features in the wsdl tool, and some other minor enhancements. The XmlSerializer also has some improvements, such as the ability to pre-generate serializers. This won`t be difficult to implement since we already have a serializer generator, and I only need to implement some methods that use that generator. There is also a new tool called sgen. If you run "sgen myassembly.dll" it will generate a new assembly called myassembly.XmlSerializers.dll that contains all serializers for all classes inside myassembly. When an application wants to serialize an......

165 of 174 | Cool XmlSerializer Features - Tim Ewald is back to blogging with a great new article:  XmlSerializer sans XSD.  After recently playing with the XML Serialization attributes on classes for a project in InfoPath, this article hits perfectly to show you how to create classes based on an existing XML File.  For my project in InfoPath I pretty much worked the opposite way and created a class with the attributes to be serialized down through a web service.  The Invoicing sample with the InfoPath SDK gives a great example of this.  I was absolutely amazed at how easy it was to point to a web service, pull down my class schema, build an InfoPath form, and shove it back up to the server without ever needing to touch XML other t......

166 of 174 | XML Infosets != (angle brackets and UTF-8) - Christian isn’t too enthusiastic about the XML Binary Characterization Working Group. Many others share his opinion and grimace whenever the idea of “binary XML” is floated. Personally, I’m not opposed to the idea of an optimized binary Infoset representation. Realistically, we already have a binary Infoset representation. It just so happens that the binary representation of XML Infosets happens to be the same as the binary representation of strings. I think there is a more optimal representation out there, and I’m glad there’s a Working Group looking in to the idea. I think a lot of people have con......

167 of 174 | it`s my turn to drive - This is my first blog entry here.First, I have to introduce myself. I am Atsushi Enomoto, llving in Tokyo. I always write Atsushi Eno (since many Japanese friends call me eno). You will find me usually logging in #mono at my working time (as `eno`).I am working on XML stuff, except for XmlSerializer (Lluis rules). When I joined to the project, XmlReader, XmlWriter, DOM and XPath are already implemented. There are great pioneers. And after a few months, Ben implemented most of the managed XSLT engine. So in fact there is not so many things what I have done. I can say I had implemented XML Schema stuff (well, schema reader and writer had been implemented as well), but the specification is wh......

168 of 174 | Serialize Arrays and ArrayLists to XML - The XmlSerializer class provides a great way to convert (serialize) objects to XML and back (deserialize). However, it can be difficult to properly serialize collections such as Arrays and ArrayLists unless you know a few tricks. This sample application demonstrates how multiple car class instances can be added into an Array as well as an ArrayList and then be serialized into an XML structure. This serialization process is accomplished by using special XML serialization attributes such as XmlArray and XmlArrayItem found in the System.Xml.Serialization namespace. For example, the following code demonstrates how the type within an ArrayList can be identified using the XmlArrayItem attrib......

169 of 174 | XmlSerializer & UTC once more - While I wasn't looking, Doug Purdy, who is the PM for the team in charge of the XmlSerializer has posted this little cryptic answer to my initial question: String serializedDateTime = XmlConvert.ToString( someDateTime ); DateTime deserializedDateTime = XmlConvert.ToDateTime( serializedDateTime ); What Doug is showing is really what the serializer is doing with dates under the hood and that I am incorrectly blaming the XmlSerializer for the lack of UTC support. [XmlConvert.ToString() also does nothing more than calling DateTime.ToString() with the appropriate format string]. As I was already saying in yesterday's post, but what I want t......

170 of 174 | XmlSerializer & UTC once more - While I wasn`t looking, Doug Purdy, who is the PM for the team in charge of the XmlSerializer has posted this little cryptic answer to my initial question: String serializedDateTime = XmlConvert.ToString( someDateTime ); DateTime deserializedDateTime = XmlConvert.ToDateTime( serializedDateTime ); What Doug is showing is really what the serializer is doing with dates under the hood and that I am incorrectly blaming the XmlSerializer for the lack of UTC support. [XmlConvert.ToString() also does nothing more than calling DateTime.ToString() with the appropriate format string]. As I was already saying in yesterday`s post, but what I want to make a......

171 of 174 | XmlSerializer Quiz: The solution - I posted a little question here, just asking "Why". For your reading convenience, I pull the code in here once more: DateTime issued; [XmlIgnore] public DateTime IssuedUtc { get { return issued; } set { issued = value; } } [XmlElement("issued")] public DateTime IssuedLocalTime { get { return Issued.ToLocalTime(); } set { Issued = value.ToUniversalTime(); } } So, indeed, why am I doing this Well, when I decided to normalize all times handled by the backend engine of dasBlog into the UTC timezone, I really didn`t think of the XML Serializer being a problem at first. It turned out to be one. The reason why I wanted al......

172 of 174 | XmlSerializer Quiz: The solution - I posted a little question here, just asking "Why?". For your reading convenience, I pull the code in here once more: DateTime issued; [XmlIgnore] public DateTime IssuedUtc { get { return issued; } set { issued = value; } } [XmlElement("issued")] public DateTime IssuedLocalTime { get { return Issued.ToLocalTime(); } set { Issued = value.ToUniversalTime(); } } So, indeed, why am I doing this? Well, when I decided to normalize all times handled by the backend engine of dasBlog into the UTC timezone, I really didn't think of the XML Serializer being a problem at first. It turned out to be one. The reason why I wanted all times ......

173 of 174 | A little XmlSerializer Quiz. - DateTime issued; [XmlIgnore] public DateTime IssuedUtc { get { return issued; } set { issued = value; } } [XmlElement("issued")] public DateTime IssuedLocalTime { get { return Issued.ToLocalTime(); } set { Issued = value.ToUniversalTime(); } }   Why? ...

174 of 174 | A little XmlSerializer Quiz. - DateTime issued; [XmlIgnore] public DateTime IssuedUtc { get { return issued; } set { issued = value; } } [XmlElement("issued")] public DateTime IssuedLocalTime { get { return Issued.ToLocalTime(); } set { Issued = value.ToUniversalTime(); } }   Why (c)2002-2004 Clemens Vasters. You want to build service oriented applications on the Microsoft .NET Framework and are not quite sure how newtelligence Workshops get you going with concrete, pragmatic guidance on today`s shipping technology stack, keeping tomorrow in perspective. Available on-site, world......