[nem-en] Multiple project solutions

[Kamil Skalski]

btw, can you explain why exactly do you need it? Is it
- the "locking" issue, you mentioned earlier, but did not explain deeper
- some memory / perf. savings
- having InternalTypes from different projects the same, so you can
test for equality between them

If this is just a problem of using  "Assembly.Load" several times on
the same assembly, then we could just make similar static / global
cache to

      unless (_loaded_assemblies_by_name.Contains (assembly.FullName)) {
        _loaded_assemblies_by_name [assembly.FullName] =
LibraryReference (this, assembly); // store the pre-loaded reference


from LibrariesLoader.n



2007/1/6, Igor Tkachev <it at rsdn.ru>:
> Hello devel-en,
>
> Michal, Kamil,
>
> We have another issue related to the multiple project solutions and we
> need your help.
>
> We can have more than one project in the same solution and each
> project has associated ManagerClass. Currently, ManagerClass can load
> types from assemblies. We need ManagerClass to be able to use types
> from other projects, I guess it should read types from other
> ManagerClasses.
>
> Can we do it?
>
> --
> Best regards,
> Igor
> mailto:it at rsdn.ru
>
>
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>


-- 
Kamil Skalski
http://nazgul.omega.pl