Bug 35093 - References to imported PCL break when editing XAML pages
Summary: References to imported PCL break when editing XAML pages
Status: RESOLVED FIXED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Xamarin.Forms ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-10-20 11:06 UTC by Sebastian Brandes
Modified: 2016-12-22 23:11 UTC (History)
5 users (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 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 Sebastian Brandes 2015-10-20 11:06:35 UTC
I am building a Xamarin.Forms application (v1.5.0) using Visual Studio 2015 and the most up-to-date Xamarin tools as of October 20, 2015.

Whenever I design XAML pages in the PCL containing most of my app logic, the references to the PCLs I have important in my main PCL break;

My solution contains the following projects:
- SurfBuddy (main PCL)
- SurfBuddy.Core (supporting PCL)
- SurfBuddy.Services (supporting PCL)
- SurfBuddy.Droid
- SurfBuddy.iOS

The references to the supporting PCLs break whenever I do some changes in the XAML editor. When I return to any of my class files I get squiggly lines under the references to my other PCLs.

See this screenshot: http://imgur.com/5HdlNbb

The only way to resolve this is by cleaning the solution and rebuilding it again. However, doing this over and over again is a little tedious.
Comment 1 Sebastian Brandes 2015-10-20 11:07:54 UTC
An important note: Despite seeing this squiggly lines I am still able to build and debug the project. It is entirely a design-time issue.
Comment 2 Sebastian Brandes 2015-10-20 12:25:24 UTC
I have recorded a screencast where I am reproducing the issue. Check it out here: https://youtu.be/UVPbCCdST94
Comment 4 Brendan Zagaeski (Xamarin Team, assistant) 2015-10-21 15:21:54 UTC
Based on a quick first glance, I think this might be a duplicate of Bug 32988. If temporarily downgrading to Xamarin.Forms 1.4.3 [1] does stop the problem for you then I think we can safely mark it as a duplicate.


Thanks!

- Brendan
Xamarin Customer Support



[1] http://stackoverflow.com/questions/5628689/download-old-version-of-package-with-nuget
Comment 5 Sebastian Brandes 2015-11-23 05:15:23 UTC
Downgrading to 1.4.3 did not resolve the issue and after upgrading to 2.0.0 (build of November 21, 2015) I still have this problem.

What kind of information do you need from me to resolve this issue?
Comment 6 Brendan Zagaeski (Xamarin Team, assistant) 2015-11-23 15:02:26 UTC
Thanks for the update. If you would be able to zip up and attach back a test case that fails for you in 1.4.3 in the same way that it fails in 2.0.0, that would be perfect.

Feel free to mark the attachment as private if you like. Also feel free to get in touch via a "Business & Enterprise Support" email [1] to help coordinate on minimizing the test case, if desired.

> [1] https://xamarin.com/support


Many thanks!
Brendan
Comment 7 Jose Gallardo 2016-12-22 23:11:05 UTC
Hi,
As we've added several improvements to our build system and deploying/debugging mechanism since the bug was reported, I'm resolving it tentatively as Fixed.
That said, if you're still facing this issue with current bits, please feel free to reopen the bug.
Thanks