XMLDOM vs System.Xml

jensthomsen

It seems like Navision is no longer using XMLDOM for parsing XML's in Nav2013 (example: Codeunit 13601 in the DK version), instead they are making use of the .NET component 'System.XML' (is that a standard Windows thing?). But from what I understand, it is still possible to use automations like XMLDOM, except in the Windows client. So: which major drawbacks are there in using XMLDOM instead of the .NET component?

deV.ch

Its way slower, it's not guaranteed to work in any future version AND most important, system.xml has almost the same methods and properties like the automation, so upgrading existing code is very simple! I would not go for Automations because of this reasons.

System.Xml is part of the .net framework, since the framework is preinstalled with windows, you could call it a 'standard windows thing'.

BardurKnudsen

...and COM is not supported on the server in NAV2013. So if you want to use XMLDOM then you have to make sure that you instantiate them on the client - which then prevents you from running the code in the background.
It not out of pure evil, that we don't support it server side: The server in NAV2013 is 64 bit (and we don't have 32 bit version). COM objects run 32 bit, and for a number of technical reasons, a 64bit process cannot host a 32 bit COM. But since the client runs 32 bit, it can also run COM.