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 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.
Created attachment 16378 [details]
Adding XAMLC to compile the XAML in a PCL project causes IDE intellisense errors similar to this:
> Error: Ambiguity between 'someElement' and 'someElement'
**Steps to Reproduce:**
1. Open the attached project in Xamarin Studio.
2. Open Case354609Page.xaml.cs
There are red lines under "TestLabel" and "InitializeComponent" with errors about ambiguity. See attached images.
No intellisense errors.
**Build Date & Platform:**
=== Xamarin Studio Enterprise ===
Version 6.0 (build 5174)
Installation UUID: e01c3049-a2d2-4e0a-aad8-afe6fb627c4d
Mono 4.4.0 (mono-4.4.0-branch-c7-baseline/5995f74) (64-bit)
GTK+ 2.24.23 (Raleigh theme)
Package version: 404000182
=== Xamarin.Profiler ===
=== Xamarin.Android ===
Version: 126.96.36.199 (Xamarin Enterprise)
Android SDK: /Users/johnmiller/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.4 (API level 19)
5.0 (API level 21)
5.1 (API level 22)
6.0 (API level 23)
SDK Tools Version: 25.1.2
SDK Platform Tools Version: 24.0.0
SDK Build Tools Version: 23.0.2
Java SDK: /usr
java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
Android Designer EPL code available here:
=== Xamarin Android Player ===
Location: /Applications/Xamarin Android Player.app
=== Xamarin Inspector ===
Build date: Thu May 12 22:20:04 UTC 2016
=== Apple Developer Tools ===
Xcode 7.3 (10183.3)
=== Xamarin.iOS ===
Version: 188.8.131.523 (Xamarin Enterprise)
Build date: 2016-06-01 21:23:15-0400
=== Xamarin.Mac ===
Version: 184.108.40.2063 (Xamarin Enterprise)
=== Build Information ===
Release ID: 600005174
Git revision: 694a75f040b7f2309bc43d4f78a3a6572ca898bf
Build date: 2016-06-01 17:28:08-04
Xamarin addins: 33f406fa2dcf214012c78cb846585f062b2e1d24
Build lane: monodevelop-lion-cycle7-baseline
=== Operating System ===
Mac OS X 10.11.2
=== Enabled user installed addins ===
Xamarin Inspector 0.8.1.0
Remove the XAMLC attribute in the AssemblyInfo.cs file and the errors go away.
Created attachment 16379 [details]
Screenshot - Actual 1
Created attachment 16380 [details]
Screenshot - Actual 2
This sounds like a duplicate of Bug 41572, one of the known issues that's now mentioned in the Xamarin Studio 6.0 release notes:
## Regression status for the test case from Comment 0: immediate regression in Xamarin Studio, not Xamarin.Forms
Based on this regression check, I am satisfied that this is a duplicate of Bug 41572 (in particular the "second part" of that bug for PCL projects, starting at Bug 41572, Comment 12), so I will mark it accordingly.
BAD: Xamarin Studio 6.0 + Xamarin.Forms 220.127.116.11
BAD: Xamarin Studio 6.0 + Xamarin.Forms 18.104.22.168
GOOD: Xamarin Studio 5.10 + Xamarin.Forms 22.214.171.124
*** This bug has been marked as a duplicate of bug 41572 ***
The problem is broader: it appears that any solution generated first in VS and then moved to XS Mac is plagued by this and no recovery lasts. Trashing bin and obj folders and re-adding packages provides one-time relief. But then, after next rebuild, error marking goes batshit crazy again, as shown in photos. This appeared in the 6.0x upgrade and persists in the current beta.
This bug has been marked as a duplicate of Bug 41572. Further updates on this issue are being tracked there. As noted in that bug, the fix for PCL projects has not yet been published to an updater channel.
I'll watch for it there: Bug 41572. Thanks.