Bug 12108 - How to check PCL Support for Android
Summary: How to check PCL Support for Android
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: 4.0.9 (from master)
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-05-06 02:54 UTC by Nischal
Modified: 2013-06-24 16:18 UTC (History)
3 users (show)

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:

Description Nischal 2013-05-06 02:54:53 UTC
We are not sure how to check PCL support for Android.

This is in the release notes:
Fixed PCL support for Xamarin.Android projects

Environment details:
X.S 4.0.5 (build 2)
Mono 3.0.11 ((no/edc181c)
Xamarin.Android 4.7.5-14
Comment 1 Jeffrey Stedfast 2013-05-06 11:54:18 UTC
Once you've created your Android project, simply try adding a "Portable Library" project (listed in the "C#" project templates section) and making sure that your main Android project can reference it.
Comment 2 narayanp 2013-05-07 01:50:53 UTC
We are able to add Portable library project reference in main Android Project.

Closing this issue.
Comment 3 PJ 2013-06-24 16:18:35 UTC
This bug was marked as fixed for Xamarin Studio 4.0.9, which is currently in the beta channel. Try it out!