Dave Crozier wrote:
Paul,
Using the SaveAsClass doesn't allow you to use other objects as properties
as it is not recursive. If I remember correctly Rick's is.
Dave, I wrote this in a related mail just recently:
I did look at using XML to persist objects (somebody did mention that
idea and referred me to Rick Strahl's wwXML class). However one problem
with Rick's class is that it can only deal with nested objects if the
XML excludes a DTD - and in that case the XML has to be used to populate
an existing object with the correct hierarchy of objects and
properties. You can restore XML to a (not currently existing) object if
the XML includes a DTD but you cannot ceate the XML+DTD *and* deal with
nested objects. IOW you can have your cake *or* you can eat it !
Dave Crozier
The secret to staying young is to live honestly, eat slowly, and to lie
about your age
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Paul Newton
Sent: 16 October 2006 16:36
To: [email protected]
Subject: Re: Persisting objects
Andy Davies wrote:
myCustomObject.SaveAsClass(ClassLibName, ClassName [, Description])
Andrew Davies MBCS CITP
- AndyD 8-)#
Obvious, really ! Makes me wonder, though, why somebody like Rick Strahl
should go to the trouble of having an Object2XML method in his wwXML class.
Thanks Andy
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
