I will close this discussion now for simplicity because today's (Sep 11, 2015) Cycle 5 – Service Release 4 brings fixes to the Stable channel for all of the VS 2015-specific issues that were being tracked in this thread.
Please discuss any new issues in XamarinVS (in any version of Visual Studio) in the general XamarinVS release announcements. Today's XamarinVS release announcement can be found here:
Upstream Release: Microsoft Visual Studio 2015 RTM
Date published: July 20, 2015
Release notes (from Microsoft): https://www.visualstudio.com/en-us/news/vs2015-vs.aspx
"Stable Release: XamarinVS 3.11.836, Cycle 5 – Service Release 3" or higher.
(Xamarin for Visual Studio "Cycle 5 – Service Release 3" includes some specific fixes for Visual Studio 2015 that are not included in the previous "Cycle 5 – Service Release 2" version.)
This first post will be updated regularly.
Hopefully this thread will help answer "what might break if I update to this release?"
If you find a new problem that is specific to Xamarin after you update to Visual Studio 2015, please provide as many details as you can about how to reproduce the problem. You may reply directly in this thread or contact the Xamarin Support Team via email.
Of course for questions and discussions about topics other than bugs, feel free start new forum threads.
Upstream Visual Studio bug here, Xamarin tracking bug here: Bug 32977 - [Visual Studio, upstream] VS 2015 hangs or crashes under certain circumstances when working on Xamarin.Forms projects. This appears to be an upstream bug in VS 2015 itself that is exposed by Xamarin's change to using Visual Studio's built-in IntelliSense for XAML pages starting in VS 2015 + Xamarin.Forms 1.5.0. Candidate fix now available in the Beta channel: the new Beta version switches XamarinVS back to using Xamarin's own Xamarin.Forms XAML IntelliSense extension as a temporary fix while waiting for the next update of VS 2015 from Microsoft. (Old possible partial workaround: disable the XAML IntelliSense (see the post later in the thread for additional details):
C:\Program Files (x86)\Microsoft Visual Studio [VSVERSION]\Common7\IDE\
devenv /updateconfigurationfrom a developer command prompt (for the relevant VS versions).
(If you have ReSharper, it might be possible to enable ReSharper's XAML IntelliSense as a replacement for the built-in IntelliSense after these steps.))
Bug 32622 - [XamarinVS] IntelliSense shows errors in VS 2015 when referencing certain types in app projects from PCL projects (due to the new Roslyn-based IntelliSense in VS 2015). (This one is a bug in the XamarinVS extensions themselves. It only affects VS 2015. Candidate fix now available in the Beta channel. After updating you might need to delete the hidden
.vs folder in the solution directory to force an IntelliSense refresh. Also be aware that Bug 32988 (mentioned below) has a different root cause and is not yet fixed. (Old workaround: see Comment 4 on the bug report.)
Example error messages:
Bug 32988 - [Xamarin.Forms] Modifying XAML files causes IntelliSense for references to other PCLs to fail in the
.xaml.cs code behind files with errors of the form "are you missing an assembly reference?" (This is a bug in Xamarin.Forms. It affects all versions of Visual Studio.) This seems to be another side effect of the same changes between Xamarin.Forms 1.4.3 and 1.4.4 that caused Bug 32341. Possible workaround: Downgrade to Xamarin.Forms 1.4.3.x (or earlier).
Bug 32341 - [Xamarin.Forms] IntelliSense on code behind files for XAML pages is not available for
InitializeComponent() or for elements of the XAML page that include the
x:Name attribute. (This is a bug in Xamarin.Forms. It affects all versions of Visual Studio.). Now fixed in Xamarin.Forms 22.214.171.12492 and higher. Also important: If your project contains any Xamarin.Forms XAML pages that still use the outdated
MSBuild:Compile Custom Tool, you will also need to update them to use
MSBuild:UpdateDesignTimeXaml (see Bug 32987 for additional details). (Old possible workarounds: Downgrade to Xamarin.Forms 1.4.3.x (or earlier), or try changing:
<Target Name="UpdateDesignTimeXaml" Condition="'$(UseHostCompilerIfAvailable)' == 'true'" DependsOnTargets="Compile"/>
<Target Name="UpdateDesignTimeXaml" Condition="'$(UseHostCompilerIfAvailable)' == 'true'" DependsOnTargets="PrepareResources; Compile"/>
[Xamarin.Forms] IntelliSense in VS 2015 does not work within XAML pages themselves, as discussed in the first comment on http://forums.xamarin.com/discussion/46185/visual-studio-2015-intellisense-regression-when-editing-xaml-files/p1. (This is a bug in Xamarin.Forms caused by a change in the "ownership" of IntelliSense from the XamarinVS extensions into the Xamarin.Forms NuGet package. It only affects VS 2015.) Now fixed in Xamarin.Forms 1.5.0-pre1. (Old workaround: see the two "answer" posts in that thread here and here).
EDIT Aug 11: Add a specific bug number for the VS hanging issue: Bug 32977.
EDIT Aug 12: Add information about outdated
MSBuild:Compile Custom Tool for Bug 32341. Add Bug 32988.
EDIT Aug 12: Add upstream VS bug for the hanging and crashing issue, and update wording accordingly.
EDIT Aug 16: Add new steps to deactivate XAML IntelliSense for Bug 32977.
EDIT Aug 20: Update workaround instructions for Bug 32977.
EDIT Aug 25: Candidate fixes for Bug 32977 and Bug 32622 now available in the Beta channel.