• Registered: 2017-04-12
  • Posts: 21

Topic: Namespace XMLDocument Missing

As it was discovered this morning that Unity 5.6 what was responsible for causing an issue when compiling to the Microsoft Hololens I downgraded from 5.6 to 5.5.1 (the same version my coworker had been on until this morning) I now can no longer compile the project because of this error (and 17 more just like it):

Assets\Infinity Code\Online maps\Scripts\XML\OnlineMapsXML.cs(57,12): error CS0246: The type or namespace name 'XmlDocument' could not be found (are you missing a using directive or an assembly reference?)

I've tried to go in and remove the #if compiler directives such that System.Xml is used instead of Windows.Data.Xml.Dom (or vice versa) but there's dozens of references and some of them don't 'update' nicely (e.g. GetSingleNode).

I will point out that the project was started on 5.5.1 and was running dual on a 5.5.1 install and a 5.6.0 install on two different machines.  But now that I've downgraded from 5.6 to 5.5, it won't build for the hololens at all. I can run it in the editor, but that's it.

  • Registered: 2015-06-23
  • Posts: 3,963

Re: Namespace XMLDocument Missing

Hello.

It is quite strange.
I made a test build in Unity v5.6, and it compiles and works in Hololens Emulator correctly.
I do not know why in your case this gives an error.
First you need to check your environment.
https://docs.microsoft.com/en-us/uwp/ap … mldocument

Kind Regards,
Infinity Code Team.

Boost your productivity a lot and immediately using Ultimate Editor Enhancer. Trial and non-commerce versions available.
  • Registered: 2017-04-12
  • Posts: 21

Re: Namespace XMLDocument Missing

Sorry, it's not a problem in 5.6, but a problem with downgrading from 5.6 to 5.5.1 (I originally installed the latest version, but had issues with the hololens: I'm still working with both a Unity and Microsoft representative to figure out the problem there).

It was that I tried to downgrade my version of Unity to match what the project was already built on and running just fine. When I did so, OnlineMaps threw errors about not being able to find XmlDocument.