Thanks for your response. Hmm, never thought of that. I don't know XSLT either though -)
>From: Graeme Foster <[EMAIL PROTECTED]> >Reply-To: dotnet discussion <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: Re: [DOTNET] Some Basic XML "Serialization" Questions >Date: Wed, 24 Apr 2002 13:02:56 +0100 > >Sidestepping the question somewhat, but you could use XSLT to transform >from >the serialized objects to your particular XML format. > >G. >-- >Graeme Foster ([EMAIL PROTECTED]) >Principal Software Engineer >Aston Broadcast Systems Ltd. (http://www.aston.tv) >Disclaimer: I really don't have a clue what I'm on about. > > >-----Original Message----- >From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of >Sam Gentile >Sent: 24 April 2002 12:52 >To: [EMAIL PROTECTED] >Subject: Some Basic XML "Serialization" Questions > > >I admit to not having done much Serialization stuff so I'm sorry if >these questions are basic but they might not be since what I am trying >to do is not .NET's standard view of Seriazation. I understand fairly >well the use of the [Serializable] attribute and the native Binary >IFormatter interface. I understand also that there is XML and SOAP >serialization. But all of these seem to serialize to the CLR's view of >an object or something with XML Schema types. What I actually have to do >is: we have some XML files that we create in our application. They were >defined before XML schema and they are not Schema compliant. I have some >.NET classes I am defining and I need to put the data/state in them >written out to these XML files in a certain format. The trick is I can't >just dump .NET's "view" of the objects. The XML files have a certain >format. Can I make use of any of XML Serialization or do I just have >"pound" XML into the files using classes in System.Xml? In other words, >how customizable is the XML serialization? Any ideas would be greatly >appreciated. > > > >***************************************************************************** >The contents of this email and any attachments are confidential. >It is intended for the named recipient(s) only. >If you have received this email in error please notify the system manager >or the >sender immediately and do not disclose the contents to any one or make >copies. > >** eSafe scanned this email for viruses, vandals and malicious content ** > >***************************************************************************** > >You can read messages from the DOTNET archive, unsubscribe from DOTNET, or >subscribe to other DevelopMentor lists at http://discuss.develop.com. --------------------- Sam Gentile .NET Consultant Co-author: Wrox Visual C++ .NET: A primer for C++ developers BLOG: http://radio.weblogs.com/0105852/ http://www.project-inspiration.com/sgentile/DotNet.htm http://www.project-inspiration.com/sgentile/ --------------------------- _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
