Bug 11454 - Clean target doesn't fully clean referenced Android libraries within App projects.
Summary: Clean target doesn't fully clean referenced Android libraries within App proj...
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.8.x
Hardware: PC Mac OS
: Low normal
Target Milestone: ---
Assignee: Mikayla Hutchinson [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2013-03-27 20:07 UTC by adam.lickel
Modified: 2014-10-30 13:56 UTC (History)
4 users (show)

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

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_REPRODUCIBLE

Description adam.lickel 2013-03-27 20:07:14 UTC
We have one main project and several secondary projects.
The secondary projects contain Android libraries.

When building, the libraries are copied into the obj and bin directories.
Subsequent builds will pick up these libraries and can even prevent the build process from running correctly.
Cleaning the .csproj should remove them.

```
$ find obj bin -type f


bin/Debug/ActionBarSherlock.dll
bin/Debug/ActionBarSherlock.dll.mdb
bin/Debug/com.rdio.android.mono-Signed.apk.fastdev
bin/Debug/Facebook.dll
bin/Debug/Facebook.dll.mdb
bin/Debug/Omniture.dll
bin/Debug/Omniture.dll.mdb
bin/Debug/Rdio.Net.Android.dll
bin/Debug/Rdio.Net.Android.dll.mdb
bin/Debug/SlidingMenu.dll
bin/Debug/SlidingMenu.dll.mdb
obj/Debug/assemblies/ActionBarSherlock.dll
obj/Debug/assemblies/Facebook.dll
obj/Debug/assemblies/Mono.Android.dll
obj/Debug/assemblies/Mono.Android.Support.v4.dll
obj/Debug/assemblies/Mono.Security.dll
obj/Debug/assemblies/mscorlib.dll
obj/Debug/assemblies/Omniture.dll
obj/Debug/assemblies/Rdio.dll
obj/Debug/assemblies/Rdio.Net.Android.dll
obj/Debug/assemblies/SlidingMenu.dll
obj/Debug/assemblies/System.Core.dll
obj/Debug/assemblies/System.dll
obj/Debug/assemblies/System.Xml.dll
```
Comment 2 Adrian Alonso 2014-10-28 13:05:09 UTC
I just followed the next steps:

1. Create an Android App
2. Add a Class Library
3. Add a reference in the App to the Class Library
4. Build the App -> The ClassLibrary1.dll was copied to the output path (bin\debug)
5. Clean the App -> All files have been deleted from the output path (bin\debug and obj) including the ClassLibrary1.dll

And it worked just fine for me.

Please let me know if you're still experimenting this issue and, if this is the case, it would be great if you could provide a simple repro. Thanks.
Comment 3 Anuj Bhatia 2014-10-30 13:56:23 UTC
Hi Adrian, can you please submit your repro that you were getting a passing result with and I will verify that this is resolved using the customer source?