On Apr 26, 2012, at 7:53 PM, Matt wrote:
> I had this same problem with 4.1.0, but was able to resolve it by adding hint
> paths to my project file. Now with the latest alpha release 4.1.1, I am again
> having this problem and the hint path does not seem to fix it.
Could you please file a bug?
> I tried commenting out the ResolveLibraryProjectImports task in
> Novell.MonoDroid.Common.Targets,
You mean this?
<UsingTask
TaskName="Xamarin.Android.Tasks.ResolveLibraryProjectImports"
AssemblyFile="Novell.MonoDroid.Build.Tasks.dll" />
Don't comment out that one. :-)
Instead, you'd want to comment out the _use_ of
<ResolveLibraryProjectImports/>, i.e. this one:
<ResolveLibraryProjectImports
Assemblies="@(Reference);@(ResolvedLibraryOutputs)"
OutputDirectory="$(IntermediateOutputPath)" />
Still, anything that requires patching our .targets files isn't a great
solution...
By any chance, does your project setup resemble the one in the
"ResolveLibraryProjectImports task fails when referencing library" thread?
http://lists.ximian.com/pipermail/monodroid/2012-April/009965.html
http://lists.ximian.com/pipermail/monodroid/2012-May/009999.html
The ResolveLibraryProjectImports tries to find all assemblies that your project
references, which requires that they exist and be findable. If you have a
"normal" Project Reference (with both projects in the same solution), this will
work as expected. If you've added a .dll directly and the <Reference/> element
has a <HintPath/>, the assembly should be found. If it's a BCL assembly, it
should be found. Otherwise, we'll have no idea where to look to find the
assembly, and things will fail.
Thanks,
- Jon
_______________________________________________
Monodroid mailing list
[email protected]
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailman/listinfo/monodroid
