Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 39026 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Description of Problem:
When using PCL in Xamarin Studio 6.0, the ".Net Assembly" tab in "Edit References" is empty.
Steps to reproduce the problem:
1. Create a new Solution, and select "Portable Library" as the project type
2. Right click on the "References" folder, and select "Edit References"
3. Select the ".Net Assemblies" tab, and note that it doesn't contain any values
.Net Assemblies tab doesn't contain any libraries to reference.
.Net Assemblies tab should list available assemblies to reference
How often does this happen?
Every time I try to add .Net Assembly references to a PCL
Recording of behavior: http://screencast.com/t/1zxxyoFT
=== Xamarin Studio ===
Version 6.0 (build 4520)
Installation UUID: 17585f09-d1d5-4347-adbf-5ec6455b5399
Mono 4.3.2 (mono-4.3.2-branch/ba2e5e4) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 403020467
=== Xamarin.Profiler ===
=== Apple Developer Tools ===
Xcode 7.2.1 (9548.1)
=== Xamarin.iOS ===
Version: 188.8.131.521 (Enterprise Edition)
Build date: 2016-02-18 13:08:58-0500
=== Xamarin.Android ===
Version: 184.108.40.2064 (Enterprise Edition)
Android SDK: /Users/davidhathaway/Library/Developer/Xamarin/android-sdk-macosx
Supported Android versions:
2.3 (API level 10)
4.0.3 (API level 15)
4.1 (API level 16)
4.2 (API level 17)
4.3 (API level 18)
4.4 (API level 19)
4.4.87 (API level 20)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.2
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)
=== Xamarin Android Player ===
Location: /Applications/Xamarin Android Player.app
=== Xamarin.Mac ===
Version: 220.127.116.111 (Enterprise Edition)
=== Build Information ===
Release ID: 600004520
Git revision: a354b2cb9df4b96f50b0ccb960dbdd5a9155510c
Build date: 2016-02-18 14:52:07-05
Xamarin addins: 8e54979f23feee160d245a3c33e43e77779b1eb4
Build lane: monodevelop-lion-master
=== Operating System ===
Mac OS X 10.11.3
Darwin dwhathaway-macbook-pro.local 15.3.0 Darwin Kernel Version 15.3.0
Thu Dec 10 18:40:58 PST 2015
This is not supported in Xamarin Studio 5 or 6. Portable Class libraries cannot reference any other assembly. The assemblies they use are defined by the profile so you cannot reference other assemblies. If you expand the References - .NET Portable Subset item you will see the assemblies that are supported in the profile.
In Xamarin Studio you will have to change the PCL profile that is targeted. So in project options - Build - General you can pick Profile 7 or Profile 111 which allow the use of the System.Net.Http.HttpClient.
Visual Studio does show assemblies when you try to edit the references however selecting them will change the targeted portable profile. Xamarin Studio does not support modifying the profile from the Edit References dialog. However it does seem like a nice feature. With VS I went to the references dialog and selected System.Net.Http and then it offered to modify my PCL profile so I could use that assembly. It then changed the PCL profile to 111.
Currently not being able to select an assembly in the Edit References is by design. However it might be a good feature enhancement.