On May 1, 2012, at 8:57 PM, Matt wrote:
> Everything has worked fine this way until monodroid version 4.1. I verified
> that your solution builds fine, but it appears to require including all
> projects in the same solution. I suppose I can do it this way, but I am
> confused as to why this is required and why the requirement changed in
> monodroid 4.1.
Prior to 4.1 Class Library projects couldn't contain Android
resources/assets/etc. The 4.1 release added support for class library projects
to contain resources & assets, and it preferentially tries to use the files
from the class library project directory, which requires that it be able to
_find_ the class library project directory. :-)
I think that there's supposed to be support for embedding the resources/assets
within the assembly and extracting them at build time, so "normal"
(non-project) assembly references _should_ work, but we still need to be able
to _find_ the assembly (there's just some overhead compared to the Project
reference approach); this may require setting a HintPath on the assembly
reference:
<ItemGroup>
<Reference Include="AssemblyName">
<HintPath>Path\To\AssemblyName.dll</HintPath>
</Reference>
</ItemGroup>
It's possible that we're not checking the $(OutputPath) directory or some other
directory when trying to find assemblies. If this is the case, please file a
bug with an attached test case so that we can investigate.
Thanks,
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
