[nem-en] Multiple project solutions

[vc]

> True, this should be possible with in-memory macro definitions
> obtained from project... though it requires some work. Currently we do
> not hold the metadata of macros during their compilation - we just
> generate the classes, which contain the encoding of their
> specification.
> After we create such metadata of macros being compiled, add it into
> some collection, it could be used to inject into another project. Such
> macros could be shown as "uncompiled" in hints.

Kamil, you can do this?
Also to us is necessary API which provide support for copy TypeBuilder (and
so on) in others NamespaceTree and to delete them if they have become
outdated.