18863 – Replaced DLL, still getting "Could not load file or assembly"

Bug 18863 - Replaced DLL, still getting "Could not load file or assembly"

Summary: Replaced DLL, still getting "Could not load file or assembly"

Status:	NEW

Alias:	None

Product:	Android
Classification:	Xamarin
Component:	MSBuild (show other bugs)
Version:	4.13.x
Hardware:	PC Mac OS

Importance:	Normal normal
Target Milestone:	---
Assignee:	Jonathan Pryor

URL:

Depends on:
Blocks:

Reported:	2014-04-08 13:15 UTC by Paul Hart
Modified:	2014-04-17 15:56 UTC (History)
CC List:	1 user (show)

See Also:
Tags:
Is this bug a regression?:	---
Last known good build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Paul Hart 2014-04-08 13:15:32 UTC

I have been working on a binding for Omniture analytics. I had an old binding named "App.Android.Bindings.Omniture.dll" and now it's called "App.Android.Bindings.AdobeMobileLibrary.dll". I updated the code to work with this new SDK. There are no code errors, I just get the following error at the end of build attempt:

/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/Android/Xamarin.Android.Common.targets: Error: Error executing task ResolveAssemblyReference: Could not load file or assembly '/Users/.../App.Android/bin/Release/App.Android.Bindings.Omniture.dll' or one of its dependencies. The system cannot find the file specified. (App.Android)

Note for public purposes I renamed the name of our app to "App". 

The Omniture.dll is not listed in the References folder or in the code. I have ran clean and uninstalled the last build from my device. 

How can I clean the targets?

Comment 1 Atsushi Eno 2014-04-08 20:07:23 UTC

We are not sure why the problem happens, but as a workaround, have you tried removing "bin" and "obj" directories on the project directory where the build is broken?

Comment 2 Paul Hart 2014-04-15 14:57:23 UTC

Yes, that fixed it thanks.

Note You need to log in before you can comment on or make changes to this bug.