Resolved Management does not exist in UnityEngine.XR

Hello,

I am trying to implement

using UnityEngine.XR.Management;

in a script I am writing, but visual studio 2022 is telling me that

The type or namespace name 'Management' does not exist in the namespace 'UnityEngine.XR' (are you missing an assembly reference?)

The package has worked fine elsewhere in the project in other scripts, I don't know why it would give me this problem here.

My project is using the packages
XR Interaction Toolkit 2.0.2
XR Plugin Management 4.0.7
Oculus XR Plugin 1.10.0
OpenXR Plugin 1.2.8
Visual Studio editor 2.0.16

 

I have several that seem to come from other packages I'm using, like Oculus and Mirror. Adding an asmdef with reference to Unity.XR.Management produced hundreds of new errors that seemed to be it not playing well with the others.

 

Do you have any other suggestions, or did I perhaps mess something up in my creation of an asmdef file?

 

I've added about fifty references now and am getting the feeling that something is wrong, I am getting errors to the tune of

Assets\Scripts\VR Scripts\EnableXRInput.cs(4,19): error CS0234: The type or namespace name 'InputSystem' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)

Having to add this many items seems like something about this asmdef is off, presently it's setup is
unsafe code: no
auto referenced: yes
no engine reference: no
override references: yes
root namespace: (blank)
no constraints defined
Asm def refs:
the many I have put randing from cinemachine to oculus
Platforms: any
version defines: empty

Adding more does seem to slowly clear errors, but I sense there may be a simpler way?

 

Images:

 

Sounds a little bit like my problem I am describing here: https://forum.unity.com/threads/pro...ence-in-xr-interaction-toolkit-2-0-2.1318401/

 

It may seem cumbersome, but this is the way to work with AssemblyDefinitions. Now just make sure you also add the UnityEngine.XR.Management also. That will get rid of your errors.

AssemblyDefs. will reduce your compile times and make code dependencies much clearer. This is a powerful tool to learn and use https://docs.unity3d.com/Manual/ScriptCompilationAssemblyDefinitionFiles.html

 

I've acquired a better understanding of asmdef now, thanks. For starters, my problem was that my asmdef was in my root asset folder, not the folder with the problem script, which caused a lot more problems than it had to. The problem now is that I can't find a reference for a namespace called FreeDraw that I believe was put there by a team who worked on the project before me; I can't find it in the vs solution. Don't suppose any of you have had that problem before?

 

I ended up just shuffling some folders around and things worked out.