 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussion GroupsGeneralPHPASPPerlColdFusionFlashHTML, CSS, ScriptsBrowsers |
Webmaster Forum / ASP / General ASP Topics / September 2008Consuming XmlNode type with classic ASP.
We wrote a .NET class library that contains a class that produces an XML document. We traverse that document and set a number of properties. We wrapped the resulting DLL using COM so that we can consume it using classic ASP. All of that works just fine. We can access the XML document and all of the properties. We can load the XML into a classic ASP variant using the DOM, etc. We don't need 95 percent of the XML so we are attempting to wring out some overhead by grabbing an XmlNode from the XML document and setting it to a property. Since the DLL is returning a complex type, how can we access the XmlNode property using classic ASP? Kind of a weird one I know. Need some expert assistance here. > We wrote a .NET class library that contains a class that produces an > XML document. We traverse that document and set a number of [quoted text clipped - 7 lines] > it to a property. Since the DLL is returning a complex type, how can > we access the XmlNode property using classic ASP? Ummm...add a method to the DLL?? Why do the work in ASP if you can do it in the DLL code? Just add another method to call that allows the ASP code to select a single XmlNode. What am I missing? >> We wrote a .NET class library that contains a class that produces an >> XML document. We traverse that document and set a number of [quoted text clipped - 14 lines] > > What am I missing? The fact that its .NET dll using COM interop which will be using one of the .NET XML DOM implementation which does not support COM interop. IOW you can't return System.Xml.XmlNode from a COM component.  SignatureAnthony Jones - MVP ASP/ASP.NET > We wrote a .NET class library that contains a class that produces an > XML document. We traverse that document and set a number of [quoted text clipped - 9 lines] > > Kind of a weird one I know. Need some expert assistance here. Consider returning XmlNode.OuterXml as a string instead. Then performing a LoadXML on an MSXML document. SignatureAnthony Jones - MVP ASP/ASP.NET |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.