[Unity] Potentially Critical Failure With Assembly Definitions
Posted: 07 Nov 2018, 13:43
So, I'm hoping that this is an oversight on my part, as it seems that this is a critical issue and I have no idea how to work around it.
Due to several unity modules, I have to use assembly definitions to work with their structure. To reference certain modules, my source code has it's own asmdef; this is where my XAML also resides.
I'm aware that this is a well-documented issue, but I'm encountering problems with VS being unable to resolve a type (the name "X" does not exist in the namespace "clr-namespace:Y"), and I've done everything from ensuring CPU config for build targets to stripping the whole thing out and moving the definition around.
As a test, I explicitly added a reference to the output of the asmdef where the source is contained, and forced my local namespace to point to this assembly, and the issue was fixed. Obviously the issue is that this assembly is actually the current working assembly, it's just the compiled output, so there are duplicate definitions for everything. So it seems that VS is unable to pick up this reference without an explicit assembly reference for reasons I'm not clear on (does the Unity integration control this for example, pointing the the base C# asm? I don't see how this would affect the source, but I haven't looked into it yet).
Just to confirm, should we be able to use assembly definitions natively with Noesis, and I'm just missing something here?
Due to several unity modules, I have to use assembly definitions to work with their structure. To reference certain modules, my source code has it's own asmdef; this is where my XAML also resides.
I'm aware that this is a well-documented issue, but I'm encountering problems with VS being unable to resolve a type (the name "X" does not exist in the namespace "clr-namespace:Y"), and I've done everything from ensuring CPU config for build targets to stripping the whole thing out and moving the definition around.
As a test, I explicitly added a reference to the output of the asmdef where the source is contained, and forced my local namespace to point to this assembly, and the issue was fixed. Obviously the issue is that this assembly is actually the current working assembly, it's just the compiled output, so there are duplicate definitions for everything. So it seems that VS is unable to pick up this reference without an explicit assembly reference for reasons I'm not clear on (does the Unity integration control this for example, pointing the the base C# asm? I don't see how this would affect the source, but I haven't looked into it yet).
Just to confirm, should we be able to use assembly definitions natively with Noesis, and I'm just missing something here?