Closed andry-tino closed 7 years ago
Seems like the cause in majority of cases is wrong TypeReference
helper being constructed. The one associated to ScriptSharp is not generated, but the ordinary one is used, thus no ScriptNamespace
check is performed.
This reproes in:
Check constructed helper in factory and fix.
Add unit tests for factories (need to create mocks) and check created helper to be the expected one.
We have the ability, after semantic alignment, to detect the
ScriptNamespace
in referenced types. However this is working only if the referenced type is in the local syntax tree.If the referenced type is in the referenced assembly, then the original namespace is used even though the
ScriptNamespace
attribute was specified in that assembly's source code for that type at definition time.Example
In local syntax tree:
In the referenced assembly:
When using Rosetta and passing the assembly through
--assembly
we get: