Bug 41928 - XAMLC causes ambiguity messages in intellisense
Summary: XAMLC causes ambiguity messages in intellisense
Status: RESOLVED DUPLICATE of bug 41572
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.0
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-06-17 12:36 UTC by John Miller [MSFT]
Modified: 2016-06-23 18:30 UTC (History)
6 users (show)

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


Attachments
Sample Project (31.74 KB, application/zip)
2016-06-17 12:36 UTC, John Miller [MSFT]
Details
Screenshot - Actual 1 (75.68 KB, image/png)
2016-06-17 12:36 UTC, John Miller [MSFT]
Details
Screenshot - Actual 2 (67.93 KB, image/png)
2016-06-17 12:36 UTC, John Miller [MSFT]
Details


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 DUPLICATE of bug 41572

Description John Miller [MSFT] 2016-06-17 12:36:24 UTC
Created attachment 16378 [details]
Sample Project

**Overview:**

   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

**Actual Results:**

   There are red lines under "TestLabel" and "InitializeComponent" with errors about ambiguity. See attached images. 

**Expected Results:**

   No intellisense errors. 

**Build Date & Platform:**

XF 2.3

   === Xamarin Studio Enterprise ===

Version 6.0 (build 5174)
Installation UUID: e01c3049-a2d2-4e0a-aad8-afe6fb627c4d
Runtime:
	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 ===

Not Installed

=== Xamarin.Android ===

Version: 6.1.0.71 (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:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Xamarin Inspector ===

Version: 0.8.1.0
Hash: 95792d1
Branch: master
Build date: Thu May 12 22:20:04 UTC 2016

=== Apple Developer Tools ===

Xcode 7.3 (10183.3)
Build 7D175

=== Xamarin.iOS ===

Version: 9.8.0.323 (Xamarin Enterprise)
Hash: 39ebb77
Branch: cycle7
Build date: 2016-06-01 21:23:15-0400

=== Xamarin.Mac ===

Version: 2.8.0.323 (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

**Additional Information:**

   Remove the XAMLC attribute in the AssemblyInfo.cs file and the errors go away.
Comment 1 John Miller [MSFT] 2016-06-17 12:36:46 UTC
Created attachment 16379 [details]
Screenshot - Actual 1
Comment 2 John Miller [MSFT] 2016-06-17 12:36:59 UTC
Created attachment 16380 [details]
Screenshot - Actual 2
Comment 3 Brendan Zagaeski (Xamarin Team, assistant) 2016-06-22 16:06:43 UTC
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:

https://developer.xamarin.com/releases/studio/xamarin.studio_6.0/xamarin.studio_6.0/
Comment 4 Brendan Zagaeski (Xamarin Team, assistant) 2016-06-22 16:56:13 UTC
## 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 2.3.0.49
BAD:  Xamarin Studio 6.0  + Xamarin.Forms 2.2.0.45

GOOD: Xamarin Studio 5.10 + Xamarin.Forms 2.3.0.49

*** This bug has been marked as a duplicate of bug 41572 ***
Comment 5 Paul Mace 2016-06-23 17:42:38 UTC
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.
Comment 6 Brendan Zagaeski (Xamarin Team, assistant) 2016-06-23 17:58:52 UTC
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.
Comment 7 Paul Mace 2016-06-23 18:30:46 UTC
I'll watch for it there: Bug 41572.  Thanks.