I'm trying to instantiate a DotNet variable of type System.Xml.Linq.XElement, using this statement:
MyXElement := MyXElement.XElement('foo');
but keep getting this error message:
Ambigous function call, no matching method found.
A similar call for a System.Xml.Linq.XDocument succeeds without any problem:
MyXDocument := MyXDocument.XDocument();
XElement's factory method XElement() accepts a single XName as its parameter (in the overload that I would like to use). Normally (e.g. from C#), you pass a string to the function, which is converted implicitly to an XName - the latter class doesn't have a public constructor for me to call.
Could it be that C/SIDE is unaware of this conversion, and still expects an XName? Is there a way to work around this?
Answers
http://dynamicsuser.net/blogs/waldo/arc ... olved.aspx
It might be, but I think in my case, the parameters are overloaded, and in (e.g.) Waldo's case, it's the return value (didn't even know that was possible! :oops: ).
Jan Hoek
Product Developer
Mprise Products B.V.
http://mibuso.com/blogs/zenandtheartofc ... av2009-r2/
Jan Hoek
Product Developer
Mprise Products B.V.