How to create dotnet variable instance with no Constructors

nanda1435

Hi,

I just started moving my automations to DotNet components.

If find no Constructors for the DotNet variable "MSXML.DOMDocument.'Microsoft.MSXML, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'".

How can I create instanve of my variable?

wher can I find the documentation about the constructors for all the DotNet componets?

ara3n

xmlDom := xmlDom.XmlDocument;
xmlDom.Load('C:\Temp\NAVSetupPORT.xml');

nanda1435

I use MSXML.DOMDocument in 'Microsoft.MSXML' not the System.Xml.XmlDocument in System.Xml.
Thanks.

ara3n

Apparently you can't use it. MS uses System.xml. I suggest to use that. Is there a reason why you want to use MsXML?

nanda1435

Becuase we used "transformNodeToObject" function with the old the Automation. Now we want to replace the same with DotNet related components for all existing automations. I cann't find the similor function in System.XML. Please sugguest how can I replace the above function by using System.XML.

I have very little DotNet knoledge and only NAV.
Thanks.

ara3n

A blog with solution is coming up.

ara3n

Here is the link to the blog.

http://mibuso.com/blogs/ara3n/2012/12/0 ... -nav-2013/

MarkHamblin

nanda1435 wrote:

How can I create instanve of my variable?

wher can I find the documentation about the constructors for all the DotNet componets?

If the object does not have a constructor, there is usually a class factory to create the object type. In this case it is "MSXML.DOMDocumentClass.'Microsoft.MSXML, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'"

To create an XMLDomDocument, do this:

xmlDOM := xmlDOMConstructor.DOMDocumentClass;

Where "xmlDOMConstructor" is of type MSXML.DOMDocumentClass.

nanda1435

I now used system. xml.xmldocument. The same as in the blog. Thanks Rashed.

Information about the class is very useful in another scenario. Thanks Mark.


8)

amw79

The link to the blog doesn't work any longer. I have this problem and would like to know the answer.

RockWithNAV

Hey Nanda,

Check out the below links if it helps you anyways.

https://rockwithnav.wordpress.com/2016/02/23/consume-net-webservice-automation/

https://rockwithnav.wordpress.com/2016/02/23/consume-net-webservice-dotnet-data-type/

vaprog

Try the WayBack Machine on Reshed's link: web.archive.org/web/*/http://mibuso.com/blogs/ara3n/2012/12/07/how-to-remove-namespaces-in-xmlport-in-nav-2013/

Even though there's an answer to the original constructor question above, I would like to draw your attention to Microsoft's view on using MSXML on .NET

mdPartnerNL

vaprog wrote: »

Try the WayBack Machine on Reshed's link: web.archive.org/web/*/http://mibuso.com/blogs/ara3n/2012/12/07/how-to-remove-namespaces-in-xmlport-in-nav-2013/

Even though there's an answer to the original constructor question above, I would like to draw your attention to Microsoft's view on using MSXML on .NET

Thanks for the tip, so which dll can you still use?

vaprog

The .NET Framework classes in the System.xml namespaces should be used

, just as standard NAV does also.