Bug 11514 - Portable libraries (PCL): linker fails to find references when the PCL is already built
Summary: Portable libraries (PCL): linker fails to find references when the PCL is alr...
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: MSBuild ()
Version: 4.7.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-04-02 05:54 UTC by softlion
Modified: 2013-04-12 04:09 UTC (History)
1 user (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 FIXED

Description softlion 2013-04-02 05:54:15 UTC
I have a solution with an android project which references an android class lib which references a portable class lib (PCL).

When I build the solution the 1st time, rebuild or clean/build the solution, it compiles ok.
Then when I build the solution again (not rebuild), the linker fails complaining that interfaces and types defined in the PCL were not found.
I have to build a second time the project to get a successful build.
Comment 1 softlion 2013-04-12 04:09:46 UTC
This has been fixed in the VS2012 update 2 that is available today. It was a bug in Visual Studio Build. See http://connect.microsoft.com/VisualStudio/feedback/details/770242